Last updated: 2018-11-19

Manage the Logging Service

We designed the Logging Service for Nodinite to make sure it can be adapted for your specific demands and environment (workload), in this article you will learn how You can alter some of the settings for the Logging Service to make sure you stay compliant with formal and informal demands. Depending on your business demands and actual workload you may have to fine tune the Logging Service to match your reality. The Logging Service comes installed with default settings that gets you started.

Secure Tune Settings
Protects your data Maximizes performance General settings

Thresholds

If you are not absolutely certain and/or before you start to alter the default settings, please contact our free technical support for guidance.

Note: A restart of the Logging Service is required if you change a System Parameter

  • BizTalk Logging - Enable/Disable logging of Events with payload and context properties from Microsoft BizTalk Server

Frequently asked questions

Common problems not answered below can be found in the troubleshooting page.

How do I protect sensitive Context Values

Nodinite keeps your Context secure; Unlike for example Microsoft BizTalk Server where the Context Properties are stored in clear text perfectly readable without any traces for SQL DBA's.

With Nodinite your Context Properties from BizTalk are encrypted in our databases. In the Web Client Context properties can be masked

The Web Client provides self service access of logged data for your Users with Role based security to Log Views. An administrator may have given Users the right to view Context Data which in turn may include passwords for FTPs when for example using Dynamic Send Ports in BizTalk. You may want to mask these values for some Context Values. This setting is controlled by the 'ProtectedContextValues' System Parameter.

How do I enable/disable population of the Repository Model from Log Events?

This setting is controlled by the 'AllowRepositoryAutomapping' System Parameter.

How do I control which disks to use when the Logging Service creates new databases?

You can determine based on either amount or age when the Logging Service should spawn new Log Databases. New Log Databases are created by the Logging Service by running a DACPAC package. This process will either honor SQL Server default settings for disks to use for the Data and Transaction Log or you can provide information about your own set of disks.

This setting is controlled by the 'ImLogLocations' System Parameter.


Next Step

Web Client
System Parameters

Log Views
Log Databases
Users