How can I create an SLA for a single job that runs 144 times per day?

Products

• iDash Workload Automation

Issue/Introduction

We have a job defined in WAAE that runs 6 times per hour, every hour of the day, and every day of the week. The job runs average between <1 minute and 9 minutes. We are most interested in the job completion time, not the start time. The job runs every 10 minutes on the hour. For example: start_mins for the job are: 04,14,24,34,44,54.

How can I create an SLA for a single job that runs 144 times per day and generate a Missed SLA if the job runs longer than 10 minutes?

Resolution

At this time there is no feature function setting reoccurring hours so the only two options are:

• Create 144 separate SLAs
• Create a single SLA with 144 Time Conditions

The following example scenario is applicable to:

• Single SLA
• 144 Time Conditions
• Concerned with the job’s end time
• Job Run history averaging between 00:00:59 (job ending in less than 1 minute) and 00:09:00 (job running up to 9 minutes).
• Job scheduled to run every 10 minutes on the hour, for 24 hours.

The Key Fields are Deadline, Type, and Run validity. The following will depict 1/144 Time Conditions for the job with run times of 04,14,24,34,44,54 for each hour:  

1. Time Condition 1
2. Deadline = 00:13 ( 9 minutes added to the first run start time )
3. Type = End
4. Run validity = 9
5. Time Condition 2
6. Deadline = 00:23
7. Type = End
8. Run validity = 9

And so on for each hour until all 144 Time Conditions have been added.

The ‘end’ deadline value reflects the longest average run time of up to 9 minutes added to the job start time. Job starting at 4 minutes past midnight (00:04) allowing 9 minutes to run -> 00:13. The run validity of 9 minutes means the SLA job must complete successfully between 00:04 (starts) and 00:13 (ends) to satisfy the SLA. If a job completes outside this window, the SLA is considered Missed.