Baseline instances

更新时间:
复制 MD 格式

The system uses baseline instances to calculate the estimated completion time for each task run. This topic describes how to view baseline instance details.

Background information

Smart Baseline detects exceptions that may prevent tasks from completing on time and sends alerts in advance. This ensures the timely delivery of critical data in scenarios with complex dependencies. For more information, see Smart Baseline overview.

Limitations

Baseline instance list

  1. Log on to the DataWorks console. In the target region, click Data Development and O&M > Operation Center in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Operation Center.

  2. In the left-side navigation pane, click Task Monitoring > Intelligent Baselines.

  3. Click the Baseline Instances tab to open the baseline instances page.

    Feature

    Description

    Filters

    At the top of the Baseline Instances page, use the filters to find a specific baseline instance.

    You can filter by Data Timestamp, Owner, Event ID, Workspace, Baseline Name, Baseline Type, Priority, and Baseline Status.

    Baseline instance list

    The list displays the following details for each baseline instance: Baseline Name, Owner, Workspace, Priority, Baseline Status, Completion Status, Baseline time, Alert Contact, Alert Margin Threshold, Last Completed Instance Estimated, and Current Key Instance. In the Actions column, you can View Details, Handle a baseline instance, View Gantt Chart, and view Related Events.

    • Baseline status:

      • normal: The task finished before the alert time.

      • alerting: The task has not finished by the alert time, but the committed completion time has not yet passed.

      • overtime: The task remains incomplete after the committed completion time has passed.

      • Other: All tasks in the baseline are suspended or no tasks are associated with the baseline.

    • Est. latest instance: The task in the baseline that is predicted to be the last to finish.

    • Current key instance: The first instance on the key path of the baseline that has not run successfully. Unsuccessful states include Not Run, Waiting for Resources, Waiting for Scheduled Time, Running, and Failed.

    • Margin threshold: The time buffer between the estimated (or actual) completion time and the alert time.

      • If the baseline task is complete, margin threshold = alert time - actual completion time.

      • If the baseline task is not complete, margin threshold = alert time - estimated completion time.

      If the margin threshold is negative, the baseline is in the alerting or overtime state.

Baseline instance details

Click View Details in the Actions column of the target baseline to open the Details page.

  • General: For an hourly baseline, switch the Cycle in the upper-right corner.

    • Committed completion time: The latest time by which all tasks in the baseline must be completed. This is the guaranteed data output time.

    • Alert time: This is calculated as committed completion time - alert margin threshold.

      Note

      Set an Alert Margin Threshold for the baseline to give operations staff time to handle exceptions. The system uses this threshold to calculate the alert time (committed completion time - alert margin threshold). An alert is triggered if the system predicts a task will not be completed by the alert time. For more information, see Core logic: baseline alerts.

    • Est. latest instance: The task in the baseline that is predicted to be the last to finish.

    • Current key instance: The first instance on the key path of the baseline that has not run successfully. Unsuccessful states include Not Run, Waiting for Resources, Waiting for Scheduled Time, Running, and Failed.

    • Handler: The person who handles the current baseline alert.

  • Key Path: Displays the key path that affects the data output of the baseline. You can view the key path in a list or a Gantt chart. For more information about how the key path is determined, see Core logic: key paths and key instances.

    Note

    The Gantt chart shows both the current and historical running status of tasks on the key path.

  • History Curve: Displays the historical running status of the baseline.

  • Related Events: Displays exceptions that prevent tasks from completing on time, such as task slowdowns and errors. For more information about events, see Event alerting policies.

FAQ

Why does the Baseline Instances page show the baseline status as Empty Baseline?