Managing the Logging Service
Take full control of your Nodinite Logging Service to ensure it meets your organization's unique requirements for security, compliance, and performance. This page explains how to fine-tune and secure the Logging Service, empowering you to maximize uptime and efficiency in your integration landscape.
What you'll gain from this page:
✅ Easily adapt the Logging Service to your business and technical needs
✅ Fine-tune system parameters for optimal performance and compliance
✅ Secure your logging environment and control sensitive data access
✅ Access expert support for advanced configuration
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 to alter key settings for the Logging Service to stay compliant with formal and informal demands. Depending on your business needs and actual workload, you may need to fine-tune the Logging Service to match your reality. The Logging Service comes installed with default settings to get you started.
| Secure | Tune | Settings |
|---|---|---|
| Protects your data | Maximizes performance | General settings |
Thresholds
Before changing default settings, we recommend contacting our free technical support for expert guidance to ensure your configuration aligns with best practices.
- System Parameters – Use the Install and Update Tool to change any of the following system parameters:
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
Find answers to common questions and troubleshooting tips on 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 and are perfectly readable without any traces for SQL DBAs, Nodinite encrypts your Context Properties from BizTalk 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 'LogLocations' System Parameter.