When cron tasks fail to run successfully, the root logger cron task can be set to different levels to obtain more detailed logs. If a particular cron task fails to run successfully, additional loggers can be set up to isolate the cause of the failure.
The following table lists the application area, the cron task, a description of the cron task, and the log levels to set each logger to. The list details the key cron tasks and not contain all of the cron tasks.
Group / Area | Cron task | Description | Loggers and log level |
---|---|---|---|
Escalation | ESCALATION | Runs active escalation definitions and starts actions and notifications |
To isolate execution errors with escalations, set the child logger of cron task root logger to DEBUG level. |
Email listener | LSNRCRON | Runs periodically to process incoming emails and create or update Service Requests |
To isolate execution errors with the email listener, set the child logger of cron task, EmailListnerCron to DEBUG level. |
Integration | FLATFILECONSUMER | Automates the processing and loading of data contained in flat files |
To isolate execution errors with the integration framework, set the integration root logger to DEBUG level. This logger supports log statements produced from all of the integration framework cron tasks. |
Integration | IFACETABLECONSUMER | Automates the processing and loading of data contained in interface tables |
To isolate execution errors with the integration framework, set the integration root logger to DEBUG level. This logger supports log statements produced from all of the integration framework cron tasks. |
Integration | JMSQSEQCONSUMER | Automates the processing of messages from the JMS sequential queue in the integration framework |
To isolate execution errors with the integration framework, set the integration root logger to DEBUG level. This logger supports log statements produced from all of the integration framework cron tasks. |
Integration | XMLFILECONSUMER | Automates the processing and loading of data contained in XML formatted files |
To isolate execution errors with the integration framework, set the integration root logger to DEBUG level. This logger supports log statements produced from all of the integration framework cron tasks. |
Reporting | REPORTLOCKRELEASE | Determines whether locked report jobs continue, or are canceled and resubmitted to the reporting queue |
To isolate execution errors with reporting, set the child logger REPORTLOCKRELEASE for the cron task root logger to DEBUG. |
Reporting | REPORTOUTPUTCLEANUP | Automates the clean-up of previously output report entries that are stored |
To isolate execution errors with reporting, set the child logger REPORTOUTPUTCLEANUP for the cron task root logger to DEBUG. |
Reporting | REPORTSCHEDULE | Automates the removal of report usage entries that are created each time a report is run |
To isolate execution errors with reporting, set the child logger REPORTSCHEDULE for the cron task root logger to DEBUG. |
KPI | KPICronTask | Refreshes KPI values periodically |
To isolate execution errors with KPI, set the child logger KPICronTask for the cron task root logger to INFO. |
User group/synchronization | LDAPSYNC | Automates the synchronization of users and groups maintained in an LDAP directory |
To isolate execution errors with security, set the child logger LDAPSYNC for the cron task root logger to DEBUG. |
User group/synchronization | VMMSYNC | Automates the synchronization of users and groups maintained in an LDAP directory |
To isolate execution errors with security, set the child logger VMMSYNC for the cron task root logger to DEBUG. |
Inventory | ReorderCronTask | Runs the reorder process for direct issue items |
To isolate execution errors with inventory, set the child logger, INVENTOR for the application root logger to DEBUG. |