Overview
Application Event Logs
Validatar automatically captures detailed application events to help you monitor system activity and troubleshoot issues. These events are exported to log files, with one file generated per day for easy organization and review. Historical log files are automatically deleted after 31 days.
Log Levels
Validatar generates application events at four different levels:
- Error – Critical issues that prevent normal operation or cause failures
- Warning – Potential problems or unexpected conditions that don't stop functionality
- Information – General application activities and significant operational events
- Debug – Detailed diagnostic information useful for troubleshooting
Default Configuration
By default, Validatar is configured to capture only Error and Warning events in the log files. This keeps log file sizes manageable while ensuring critical issues are always recorded.
What Gets Logged
The log files capture a wide range of application events, including:
- System errors and exceptions
- User authentication and access events
- Data processing activities
- Integration and connection events
- Application start/stop events
The specific events logged depend on your configured log level and the operations being performed in your Validatar environment.
Changing the Log Level
If you need more detailed logging for troubleshooting purposes, you can adjust the log level to include Information or Debug events.
To change the log level:
- Open the c:\inetpub\Validatar\core\appsettings.json file in Notepad. Adjust the path if you installed Validatar in a different folder or drive.
- Change the MinimumLevel setting to one of the following: Error, Warning, Information, or Debug.
- Save your changes to the appsettings.json.
- Recycle the Validatar application pool in IIS to pick up the new changes
Note: Enabling Debug-level logging will significantly increase log file size. We recommend only using this level temporarily when working with Validatar support to diagnose specific issues.