Plant Integrations (connector) logs
Logging
Log file types and format
Connector generates two different types of log files with separate numbering sequences:
Text logs (.txt)
Traditional human-readable log files with the naming convention connector.log_<id>.txt
JSON logs (.json)
Structured, machine-readable log files with the naming convention connector.log_<id>.json
The JSON files contain the same log entries as the corresponding text logs but in a structured format that enables:
Enhanced log processing and analysis
Integration with log aggregation tools
Advanced diagnostics and automated parsing
By default logs are rotated at when they reach 20Mb and a maximum of 31 files of each are kept.
Rotation settings
By default:
Logs rotate when they reach 20MB in size
A maximum of 31 files of each type are retained
Older files are automatically deleted when the limit is reached
Log Level
Changing the log level can be done by doing a PUT on the connector API (via Swagger) at the /api/logging/loglevel endpoint. By default, the log level is set to Information.
The following log levels are supported:
Level | Description |
|---|---|
Fatal | Critical errors that typically lead to application termination. |
Error | Error events indicating failures within the application. |
Warning | Indications of potential issues that are not visible to end users. |
Information | Logs Information, Warning and Error messages. Also records all requests to Plant Integrations and their execution time. |
Debug | Logs Debug, Information, Warning and Error messages. Useful for debugging purposes. Note: Debug mode can impact performance and should only be used temporarily on production systems. |
Verbose | Logs all messages, including highly detailed information that may contain points data. Note: Verbose mode has a significant performance impact and should not be used in production except for very short periods. |