Log levels

Trace

Logs that contain the most detailed messages. These messages may contain sensitive application data like actual received values, which is why these messages should not be enabled in production environment.

Note: Trace is translated to Verbose in the log file.

Debug

Logs that can be used to troubleshoot data flow issues by recording metrics and detailed flow related information.

Information

Logs that track the general flow of the application. Any non-repetitive general information like the following can be useful for diagnosing potential application errors:

• Version information related to the software at startup

• External services used

• Data source connection string

• Number of measurements

• Egress URL

• Change of state "Starting" or "Stopping"

• Configuration

Warning

Logs that highlight an abnormal or unexpected event in the application flow that does not otherwise cause the application execution to stop. Warning messages can indicate an unconfigured data source state, an insecure communication channel in use, or any other event that could require attention but that does not impact data flow.

Error

Logs that highlight when the current flow of execution is stopped due to a failure. These should indicate a failure in the current activity and not an application-wide failure. It can indicate such failures as an invalid configuration, unavailable external endpoint or an internal flow error.

Critical

Logs that describe an unrecoverable application or system crash or a catastrophic failure that requires immediate attention. This can indicate application wide failures like beta timeout expired, unable to start self-hosted endpoint, unable to access vital resource (for example, Data Protection key file), and so on.

Note: Critical is translated to Fatal in the log file.

None

Logging is disabled for the given component.