ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SLAs not being tracked


Article ID: 195264


Updated On:


iDash Workload Automation for CA 7


Had several CA7 jobs that missed their SLA this morning. However, iDash doesn't show they were being tracked and no alerts were generated. The CA7 scheduled job did execute and several of the jobs that were part of that schedule show in the SLA trending report.  Tracking was okay up to 06/30 and appear to be okay for tomorrow. There are 2 things that I noticed. The CA7 calendars were resolved last night just after midnight. The jobs in question all had target times over 24:00. Would this cause an issue with monitoring?


Release : 12.0



The best way to avoid this would be to run the resolve command in CA 7 earlier. 

The problem is that CA 7 calendars run 1/1 to 12/31 or 7/1 to 6/30. When iDash is approaching the end of that range, say on 6/30 or 12/31, and it needs to use the calendar to find the next expected time for something to happen (for example an SLA with deadline above 24:00, so that it's expected deadline is beyond the date change), the calendar will not contain that value. So, iDash will find nothing and (in the case of SLA scheduling) assign a far future date to the next run time for the SLA. 

For SLAs with a deadline over 24:00, this could be seen the day before that calendar expires. For deadlines over 48:00, it could be two days before it expires, etc.

Running the RESOLV earlier, so that iDash will have a delta for the job containing a calendar that goes beyond 12/31 or 6/30 would fix the issue.