For the complete documentation index, see llms.txt. This page is also available as Markdown.

Diagnostic logs

Diagnostic logs are automatically recorded information about the application's operation – e.g. the executed process steps, system messages, errors, or response time.

Logs are used to analyze problems (e.g. why a given request ended with an error), monitor the correctness of business processes, and support IT teams in quickly finding the causes of errors and incidents. They help ensure the stability and security of the application.

Logging levels

  • INFO – standard information about the course of operation,

  • DEBUG – details for developers; usually disabled in production so as not to generate excess data.

  • WARN – warning. The system is working, but something has appeared that may indicate a potential problem.

  • ERROR – error. The operation failed.

Logger in low code

  • Logger in the local data source of the data model

  • Loggers in ScriptCode (scripts, validators, script tasks) - Logging in ScriptCode (Logs in unit tests of scripts/validators - Script unit tests)

Last updated

Was this helpful?