iDash Alerting differences query ""PREDICTED_MISSED_END"" and "SLA_AT_RISK_END"
Article ID: 198760
iDash Workload Automation for CA 7
We have a key batch run setup with 3 iDash definitions to handle different runs of the week. Schid=25 completes in early hours of Tue-Sat Schid=26 completes Sunday morning and Schid=27 Monday morning.
This weekend we had issues with this batch suite on Saturday (schid=26) and Sunday (schid=26) morning - but with the Saturday mornings warning of a "SLA_AT_RISK_END" and allowing time to react but on Sunday's version only a "PREDICTED_MISSED_END" was issued - followed by "SLA_MISSED_END" which alerted too late for any preventive actions to take place
On Saturday with the "SLA_AT_RISK_END" being produced and generating an alert it provided time to respond But on the Sunday morning the first and only alert was 06:02 - 2 minutes after the SLA has breached. I don't believe we create alerts from "SLA_PREDICTED_MISSED_END" - but we do from "SLA_AT_RISK_END"
Are you able to say why there would have been no "SLA_AT_RISK_END" message from the Sunday morning run?
Release : 12.1
Component : CA WORKLOAD AUTOMATION iDASH FOR CA 7
The forecasted SLA statuses don't behave in a hierarchal or linear fashion from one to the next. Depending on what's going on with the job run, forecast cycle you can skip forwards or backward on the SLA's status not hitting all the possible statuses.