On occasion, the date scheduling parameters for an SLA may expire or become invalid. Here are a couple of examples of when this can occur...
The SLA job runs on a calendar that runs out of days
The schedule in CA7 is modified to where the triggering job for an SLA no longer triggers the SLA job.
When this situation occurs, the SLA no longer tracks in iDash and no alert is generated as a result. This document provides some methods for identifying SLAs that are in this condition so that corrective action can be taken.
When an SLAs date scheduling parameters no longer allow iDash to determine a normal date to track the SLA, the future date is set to 01/2038. Therefore, this date can be used to find SLAs that are in this condition.
Method 1: Search the %IDASH_HOME%/info.log
In the info.log, the following line is posted for an SLA when this occurs...
18-08-01 23.26.45 [ INFO] idash-SLA-processing: Future SLA:**SLA Name Goes Here***^***Instance Name***-20380119-XXXX
The message above can be searched in the logs on a regular basis to identify SLAs that have the next monitoring date set in 01/2038.
NOTE: The actual day in GMT is 01/19/2038. However, depending on your iDash server's timezone, the actual day may vary. Therefore, it is best just to look for 01/2038 which is sufficient to identify this scenario.
Method 2: Use the iDash GUI Dashboard
In the Dashboard, click on the upper-right to adjust the time filter. Set the future hours to a very large number that would push past 01/19/2038...such as 200,000...
<Please see attached file for image>src="http://ca--c.na60.content.force.com/servlet/rtaImage?eid=ka00c000000ysir&feoid=00N0c00000B92wh&refid=0EM0c000001YXTk">