iDash Alerting differences query ""PREDICTED_MISSED_END"" and "SLA_AT_RISK_END"
Article ID: 198760
Updated On:
Products
iDash Workload Automation for CA 7
Issue/Introduction
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
JOB SLA SCHID ENABLED
COMMERCIAL_CREDIT_SCHID_25 DA00OPNE 25 YES
COMMERCIAL_CREDIT_SCHID_26 DA00OPNE 26 YES
COMMERCIAL_CREDIT_SCHID_27 DA00OPNE 27 YES
COMMERCIAL_CREDIT_SCHID_25
Job: DA00OPNE
SLA SchID: 25
Instance: YELLOW
Time zone: Europe/London
Enabled: Yes
Description: COMMERCIAL CREDIT (Mon - Fri)
Date scheduling
Triggering job: DA00OPNC
Triggering job SchID: 25
Deadline Type Start tracking End tracking At risk warning Run validity Past hours
30:00 End default 480m 60m 660m 13h
Saturday 15th August
05.01.05 STC49414 CAL2M649I ISLA006W SLA_AT_RISK_END 721
721 SLA ID=COMMERCIAL_CREDIT_SCHID_25¬YELLOW-20200815-0600
721 JOB= DA00OPNE
721 SchID= 25
721 Deadline=2020-08-15 06:00 +0100 :
721 iDash server=UKFHPAPIDA01 :
721 Next forecasted completion:2020-08-15 05:24:Warning:60 Minutes
Alert generated at 05:01 - IDASHSLA AT_RISK_END NAME=COMMERCIAL_CREDIT_SCHID_25 DEADLINE=2020-08-15 06:00 ACTION:CALL EGOC. KB:KB0018490
End job DA00OPNE completed 0540 - within the 6am SLA
COMMERCIAL_CREDIT_SCHID_26
Job: DA00OPNE
SLA SchID: 26
Instance: YELLOW
Time zone: Europe/London
Enabled: Yes
Description: COMMERCIAL CREDIT (Saturday)
Date scheduling
Triggering job: DA00OPNC
Triggering job SchID: 26
Deadline Type Start tracking End tracking At risk warning Run validity Past hours
30:00 End default 480m 60m 1080m 18h
Sunday 16th August
05:01 "PREDICTED_MISSED_END" reported rather than "SLA_AT_RISK_END"
05.01.26 STC27427 CAL2M649I ISLA005W SLA_PREDICTED_MISSED_END 664
664 SLA ID=COMMERCIAL_CREDIT_SCHID_26¬YELLOW-20200816-0600
664 JOB= DA00OPNE
664 SchID= 26
664 Deadline=2020-08-16 06:00 +0100 :
664 iDash server=UKFHPAPIDA01 :
664 Next forecasted completion:2020-08-16 06:43
at 06:02 "SLA_MISSED_END" generated
06.02.39 STC27427 CAL2M649I ISLA004E SLA_MISSED_END 228
228 SLA ID=COMMERCIAL_CREDIT_SCHID_26¬YELLOW-20200816-0600
228 JOB= DA00OPNE
228 SchID= 26
228 Deadline=2020-08-16 06:00 +0100 :
228 iDash server=UKFHPAPIDA01 :
228 Next forecasted completion:2020-08-16 08:11
Alert generated - IDASHSLA MISSED_END NAME=COMMERCIAL_CREDIT_SCHID_26 DEADLINE=2020-08-16 06:00 ACTION:CALL EGOC. KB:KB0018490
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?
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
JOB SLA SCHID ENABLED
COMMERCIAL_CREDIT_SCHID_25 DA00OPNE 25 YES
COMMERCIAL_CREDIT_SCHID_26 DA00OPNE 26 YES
COMMERCIAL_CREDIT_SCHID_27 DA00OPNE 27 YES
COMMERCIAL_CREDIT_SCHID_25
Job: DA00OPNE
SLA SchID: 25
Instance: YELLOW
Time zone: Europe/London
Enabled: Yes
Description: COMMERCIAL CREDIT (Mon - Fri)
Date scheduling
Triggering job: DA00OPNC
Triggering job SchID: 25
Deadline Type Start tracking End tracking At risk warning Run validity Past hours
30:00 End default 480m 60m 660m 13h
Saturday 15th August
05.01.05 STC49414 CAL2M649I ISLA006W SLA_AT_RISK_END 721
721 SLA ID=COMMERCIAL_CREDIT_SCHID_25¬YELLOW-20200815-0600
721 JOB= DA00OPNE
721 SchID= 25
721 Deadline=2020-08-15 06:00 +0100 :
721 iDash server=UKFHPAPIDA01 :
721 Next forecasted completion:2020-08-15 05:24:Warning:60 Minutes
Alert generated at 05:01 - IDASHSLA AT_RISK_END NAME=COMMERCIAL_CREDIT_SCHID_25 DEADLINE=2020-08-15 06:00 ACTION:CALL EGOC. KB:KB0018490
End job DA00OPNE completed 0540 - within the 6am SLA
COMMERCIAL_CREDIT_SCHID_26
Job: DA00OPNE
SLA SchID: 26
Instance: YELLOW
Time zone: Europe/London
Enabled: Yes
Description: COMMERCIAL CREDIT (Saturday)
Date scheduling
Triggering job: DA00OPNC
Triggering job SchID: 26
Deadline Type Start tracking End tracking At risk warning Run validity Past hours
30:00 End default 480m 60m 1080m 18h
Sunday 16th August
05:01 "PREDICTED_MISSED_END" reported rather than "SLA_AT_RISK_END"
05.01.26 STC27427 CAL2M649I ISLA005W SLA_PREDICTED_MISSED_END 664
664 SLA ID=COMMERCIAL_CREDIT_SCHID_26¬YELLOW-20200816-0600
664 JOB= DA00OPNE
664 SchID= 26
664 Deadline=2020-08-16 06:00 +0100 :
664 iDash server=UKFHPAPIDA01 :
664 Next forecasted completion:2020-08-16 06:43
at 06:02 "SLA_MISSED_END" generated
06.02.39 STC27427 CAL2M649I ISLA004E SLA_MISSED_END 228
228 SLA ID=COMMERCIAL_CREDIT_SCHID_26¬YELLOW-20200816-0600
228 JOB= DA00OPNE
228 SchID= 26
228 Deadline=2020-08-16 06:00 +0100 :
228 iDash server=UKFHPAPIDA01 :
228 Next forecasted completion:2020-08-16 08:11
Alert generated - IDASHSLA MISSED_END NAME=COMMERCIAL_CREDIT_SCHID_26 DEADLINE=2020-08-16 06:00 ACTION:CALL EGOC. KB:KB0018490
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?
Environment
Release : 12.1
Component : CA WORKLOAD AUTOMATION iDASH FOR CA 7
Resolution
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.
Feedback
Yes
No
Powered by
