Viewing the Jobstream Details - Alerts

{"URL":["/aai/web/v2/jobstreams/*/alerts"],"heroDescriptionIdentifier":"ice_description_jobstreram_definitions_alerts","customCards":[{"id":"ice_description_jobstream_definitions_alerts_list","title":"Working with the Alerts List","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/TERMA_DOCU/*.*/AAI%20Guides/Content/Jobstreams/Jobstreams_Definitions_Details_Alerts.htm"},{"id":"ice_Types_of_Alerts","title":"Types of Alerts","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/TERMA_DOCU/*.*/AAI%20Guides/Content/Jobstreams/Jobstreams_Adding_Editing_Alerts.htm"},{"type":"link","link":"https://simlabs.aod.broadcom.com/managing-sla-using-aai","languages":["en-us"],"title":"Hands-On Practice: Managing SLAs using AAI"},{"id":"ice_description_Working_w_Tables","title":"Working with Tables","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/TERMA_DOCU/*.*/AAI%20Guides/Content/_Common/CommonFunctions/CF_Working_with_Tables.htm"},{"id":"ice_description_Exporting_Table_Data","title":"Exporting Table Data","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/TERMA_DOCU/*.*/AAI%20Guides/Content/_Common/CommonFunctions/CF_ExportingTableData.htm"}]}

The Alerts tab of a jobstream details is a helpful tool for understanding and managing your alert strategy for the jobstream because you can see all the alerts that have been triggered for the jobstream as far back as 180 days. On this tab you have a table of the alerts with over a dozen columns of details about when the alert was triggered and other aspects of the jobstream run when the alert was triggered, such as the predicted end time, or the total number of jobs, the number of completed jobs, the percentage completed, and so on.

You can filter and sort the table and reorder the Alerts list to gain focused insights on the jobstream run performance or the alert strategy. With this information, you can do the following:

  • Discover patterns that point to problems or inefficiencies, or that reveal an effective alerts strategy

  • Determine whether the alerting strategy is tracking and communicating valuable information about the runs, or whether it is creating an unnecessary alert storm or failing to communicate helpful run state and status changes. This helps you understand where you might want to add, remove, or modify alert settings for the jobstream.

  • Use temporarily modified alert settings after changing a jobstream definition (such as add trimming) or the underlying job definitions so you can get feedback during monitoring about the impact of those changes on the jobstream runs.

Like any table, you can also export your Alerts list to get a CSV to share with your team or use in external tools or scripts.

This topic describes what you find on the Alerts tab and what that can tell you about the jobstream runs they are triggered in.

Accessing the Jobstream Alerts Tab

You access the jobstream Alerts tab when you open the jobstream details and then select the tab. You can open the jobstream details for a specific jobstream from various placed in AAI, as follows:

  • From any of the pages that you open from the left navigation under Jobstreams

    1. In the left navigation pane select Jobstreams, and then select one of the following:

      • Jobstream Definitions

      • Jobstream Runs - Timeline

      • Jobstream Runs - Grid

    2. In the resulting view, click the name of the jobstream that you are interested in.

    3. On the jobstream detail page, open the Alerts tab.

  • From the job details of any job that runs withing the jobstream

    1. Open the Job details.

    2. Open the Related Jobs and Jobstreams tab

    3. In the Part of Jobstreams section, if the jobstream is listed, click the Jobstream Name.

  • From the Gantt view of a specific run for the jobstream

    1. In the title bar, where you see the jobstream name, click the vertical ellipsis (three dot) icon to open an action menu , and select Open Jobstream in New Tab.

    2. Open the new tab.

The Alerts List

The list of alerts provides the following information:

  • Alert Time (always shown): The time at which the alert was issued.

  • Elapsed Time: The amount of time that the jobstream has been running since the start time.

  • Severity (always shown): The severity of the alert, shown with the corresponding severity icon.

  • % Completed: How much of the jobstream has completed expressed as a percentage. AAI uses the following dates to calculate this percentage:

    • Jobstream Start Time

    • Jobstream Predicted End Time

    • As of time, which is the time at which AAI last polled the data from the underlying scheduler. The scheduler might be a few seconds ahead of this time because AAI polls its data every few seconds, depending on the scheduler configuration. This timestamp is available in the Schedulers list in the Event as of column. For more information, see Schedulers.

  • Type (always shown): The type of the alert. For more information, see Types of Alerts.

  • Start Time: The time at which the jobstream run started.

  • Predicted End Time

    predicted end time

    Time at which the target job is predicted to finish. This time determines whether the jobstream will meet the SLA or not.

  • Jobstream Run ID

    The unique internal ID in AAI for the jobstream run. This is also a link to the Gantt view for the run. For more information, see The Gantt View for a Jobstream Run.

  • Completed Jobs

    Number of jobs that have already completed in the run of the jobstream for which the alert was sent.

  • Currently Running Jobs

    Names of the jobstreams that are currently running in the jobstream.

  • Jobs in Jobstreams

    Total number of jobs contained in the jobstream.

  • Running Job Counts

    Number of jobstreams that are currently running in the jobstream.

  • Early/Late

    Current prediction of how early or late the jobstream is expected to complete.

  • Average End Time

    Time at which the jobstream is expected to finish, based on the available history for the jobstream and the time the run started.

  • Late End Time

    Late Criterion as defined for the jobstream when configuring its parameters. This is the time as of which AAI considers this jobstream to be late. For more information, see Configuring Jobstream SLAs.

  • Predicted Jobs

    Number of jobs that have predicted start or end times. This number can vary because it takes into consideration any job failures that may have occurred or other dependency definitions that could influence the path of the jobstream.

When Is the Alerts List Empty?

The Alerts list can be empty for several reasons:

  • No alerts of any type are defined for the jobstream.

  • The jobstream runs to date have not triggered any of the alert types that are defined for the jobstream.

  • The filter that is applied excludes all alerts for the jobstream.

  • The alerts were cleared by AAI when the jobstream was rebuilt due to certain changes such as modifying trimming or start jobs, or rebuilding the jobstream with a different start date or days of run history.

Types of Alerts

AAI can issue the following types of jobstream alerts based on the events in the jobstream runs. Note that alert types need to be defined and activated on the Deadlines & Rules tab of the jobstream details. Jobstream alerts fall into three alert categories, which reflect their purpose:

  • Start By Alerts

    This alert type applies only when you have Start By alerts defined for SLAs in the jobstream.

    • Late Start Time

      This is tied to any Start By conditions that are set for the SLA that applies to a specific jobstream run. While the Start By conditions are defined with the SLA deadlines, this is where you define whether alert notifications are sent and how, as well as the severity. The settings here apply to all Start By conditions for all the SLAs defined for the jobstream. The default severity is Normal.

  • SLA Alerts

    These alert types monitor the progress of a jobstream run in relation to meeting its SLA deadline.

    • Predicted Late (previously called "Late")

      These alerts build early warning systems.

      For long-running processes, the AAI prediction engine can determine that an SLA is in jeopardy long before the SLA is due. This is possible because AAI uses actual, real-time data to perform its calculations and this data come from the scheduler.

      Late alerts are generated as soon as the AAI prediction engine determines that the SLA for this run will not be met. The default severity is Critical.

    • Back on Track

      After a Predicted Late alert has been sent, if a subsequent calculation of the prediction engine determines that with the most recent circumstances the run can be expected to finish by its SLA deadline, then this alert notifies that the jobstream is predicted to be back on track. A jobstreams anticipated end time can change between predictions due to any number of factors, such as an on-hold job is reset to run, key job executions run sooner or shorter than anticipated, or even that the processing path changes due to some logic. The default severity is Critical.

    • Exceeded Deadline (previously called "Exceeded SLA")

      AAI sends this alert when the jobstream run reaches the time of its SLA deadline and the target job has not yet completed successfully. The default severity is Critical.

  • Run Alerts

    These alert types monitor the progress of the jobstream run towards completion, irrespective of the impact to meeting the SLA deadline.

    • Complete

      This alert informs you that the jobstream run is complete. Like the Started and Target Job Started alerts, this can be a useful information alert for high-profile or critical business processes. It is sent every time a run of the jobstream cpmpletes. Its default severity is Normal.

    • Not Predicted to Finish

      A number of conditions during runtime could cause AAI to predict that the target job will not successfully complete (for example, an upstream job fails and the target job depends on the successful completion of that job and all of its downstream jobs). This alert is sent in these cases. The default severity is Critical.

    • Started  

      This alert informs you that the jobstream run has started. Like the Complete and Target Job Started alerts, this can be a useful information alert for high-profile or critical business processes. It is sent every time a run of the jobstream starts. The default severity is Normal.

    • Target Job Started

      This alert informs that the target job of in the jobstream has started. Like the Started and Complete alerts, this can be a useful information alert for high-profile or critical business processes. It is sent every time the target job of a run of the jobstream starts. The default severity is Normal.

See also: