Configuring Jobstream SLAs
Every jobstream has at least on e SLA defined for it when the jobstream is created. You can modify its configuration settings and add more SLAs for different days of the week. You add and edit SLAs for a jobstream from the Deadlines & Rules tab of the jobstream details. . This topic explains how to add and edit SLA configurations for a jobstream to create an entire SLA strategy for the jobstream. As SLAs define deadlines for jobstream runs, you can also defined alerts to track and notify operators and other stakeholders about the jobstream adherence to the deadlines. You do that from the same Deadlines & Rules tab. For information, see Defining Alerts for a Jobstream.
Watch the Video: Defining Multiple SLAs
SLA Types Define How the SLA Is Calculated
When editing a jobstream, you can define how the SLA deadline is determined. The default SLA that is assigned is determined by the system based on aggregated historical data of all the jobs in the jobstream. You can override the system-determined type when you edit the SLA. When you have multiple SLAs for one jobstream, you cannot mix calculated end times with fixed duration SLAs because that can collision on jobstream views and calculations.
The SLA types are as follows:
-
System-calculated
Select this option if you want AAI to decide which method is the best one to determine when it will consider this jobstream to be late. AAI's algorithm chooses the best criteria based on the historical data that it has collected in its database.
Depending on the method that it has chosen, AAI then displays either the late time, the average end time or the average duration. It also indicates what method the late criterion calculation is based on.
-
User-supplied End Time
Enter the end time as of which you want AAI to consider the target job to be running late.
If you need to display the times in a time zone that is different from the target job's time zone, select it from the Time Zone dropdown list.
Once you have selected the end time, AAI displays the average end time (and the standard deviation) for the jobstream based on the historical data contained in its database. This information helps you select a reasonable end time for the jobstream.
The Options button opens the End time options dialog, where you can further manipulate the end time by selecting the Override automation calculations checkbox. Since the AAI prediction engine calculates this value automatically, we do not recommend using this option.
In Jobstream completes nn calendar day(s) after jobstream starts you can enter the number of calendar day(s) after the jobstream starts that the jobstream end time will be determined by. For example, if a jobstream starts to run at 11:00 p.m. on Monday, and the end time should be at 5:00 a.m. on Tuesday, then you would enter a 1 in the calendar day(s) after jobstream starts field in order to accurately reflect the proper end time.
Tip:You may want to define jobstreams that are based on daily and end of month (or other similar criteria). Using the same Target Job, you can create different jobstreams that have different user-defined end times (i.e., with End Of Month having a later end time). This can help prevent unnecessary alerts for Month End processing.
-
User-supplied Fixed Duration
Specify how long the jobstream can execute before AAI considers it to be late. AAI displays the average duration (and the standard deviation) for the jobstream based on the historical data contained in its database. This information helps you select a reasonable duration for the jobstream.
See also: