Escalation loggers
If an escalation fails to run, the failure can be caused by the escalation engine, the email notifications, or actions triggered by the escalation. You can troubleshoot the cause of the failure by setting the correct log level.
The following table lists the escalation loggers, a description of the logger, and the log level to set each logger to.
| Logger | Description | Log level |
|---|---|---|
| crontask | Root logger that generates log statements for all cron tasks | DEBUG |
| ESCALATION | Child logger that inherits from cron task root logger and generates log statements specifically for the escalation engine | DEBUG |
| sql | Root logger that generates log statements of SQL statements run in the application server | INFO |
| COMMTEMPLATE | Child logger that inherits from service root logger and generates log statements specifically for communication templates and notifications events | INFO |
| Root logger that generates log statements for communication with the mail server when sending notifications. | DEBUG |