You can monitor the execution of escalations by the escalation engine. To do so, you can configure logging and examine the log files for log statements related to the escalation engine.
To enable escalation engine logging, you use the Logging application. For each of the loggers set the wanted log level. If the logger does not exist, create your own logger. Verify that the loggers are all active. Associate an appender with a logger to ensure that log statements send to a product log file. When you save your changes, run the Apply Settings action in the Logging application for the settings to take effect immediately.
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 |