How to change the connector log level?
Connector log level determines how much information the system records during operation. Adjusting this level can be useful for troubleshooting issues, but higher‑detail settings can affect system performance. This article explains the available log levels, when to use them, and how to reset them correctly.
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. |
Important
* Always revert the log level to Information or Warning after troubleshooting. The Debug and Verbose levels generate large amounts of data and can slow down system performance.
* When the connection pool restarts (on Web.Host) or the service stops/starts (on App.Host), the log level automatically resets to the default level.