What is the Logging Service?
Throw away your crystal ball! With Nodinite you don't have to know everything in advance since everything logged can be reindexed. so make sure you log everything(!) The benefit of having Nodinite log all your business transactions are plentiful. For starters:
- You get the Statistics and KPI's
- You can find your data and your errors
- You can get alerts for Non-Events
- You can do decision support Reporting
- You can re-index if you finds out you need yet another Search Field
- You can create payment models if you need to split costs for your system integration solutions based on your KPI's
|Protects your data||Archive||Find your data|
|Nodinite encrypts your data and the only way to read is through log audited operations||Archiving is built-in, store as much data as your business deem||Smart re-indexing support gives you the power to find what you are looking for even if it's old data|
The Logging Service is your cleaning operative and keeps Nodinite at its best
- Managing Logging Service - Tune the Logging Service to suite your needs and environment
- Logging from BizTalk - Get insights of your business transactions by logging all events from Microsoft BizTalk Server to Nodinite (in and out events with payload and context) without making changes to the existing BizTalk solutions using the built-in tracking capabilities
Nodinite Logging Service supports logging from your Microsoft BizTalk Servers where global tracking is enabled. You can concentrate all BizTalk environments to a single Nodinite instance. To keep performance goals and to scale the Logging Service runs one thread per environment with your user-defined environment specific settings. Nodinite supports multiple versions of BizTalk.
The Logging Service hosts one thread (WorkerItem) for each configured BizTalk Environment (group) to log from
This topic is further detailed in the Logging from BizTalk.
The performance of this service heavily depends on the current workload on CPU, memory, network, SQL and disk IO on involved machines. User Configuration that affects processing comes from Message Types and Search Fields. The amount of work also depends on the size of the payload/Context, the current amount of data in the Log Database, current workload
We have started to gather a list of KPI's, please feel to contribute:
|Average processing time||Number of messages/second||SQL Disk Read performance MB/s (Volume for FileGroup Index)||SQL Disk Write performance MB/s (Volume for FileGroup Index)||#SQL Cores||#Cores Logging Service||#RAM SQL GB (memory limited)||#RAM Logging Service GB||Comment|
|32 ms||>30||>1350||>52||2||2||7||7||Azure Demo environment|
Common problems and FAQ for the Logging Service** not found on this page can be found in the troubleshooting page.
Information about the state of the Logging Service is clearly visible for a user in the following places:
- The notification area of the Web Client
- From the Overview in the Administration of the Web Client
- On the Update page of the Install and Update Tool
The actual whereabouts of the Logging Service can be found in the following places:
- From the Overview in the Administration of the Web Client (and all other installed components)
- On the Update page of the Install and Update Tool (Core Services)
This topic is further detailed on the 'Logging from BizTalk' page.