The system uses baseline instances to calculate the estimated completion time for a node in a baseline each time. This topic describes how to view baseline instances and view the details of a baseline instance.
Background information
An intelligent baseline enables DataWorks to identify an exception that prevents a node in the intelligent baseline from being complete as expected and notifies you about the exception at the earliest opportunity. This ensures that the data you want to obtain is generated as expected in scenarios where dependencies between nodes in a baseline are complex. For more information, see Overview.
Limits
Only DataWorks Standard Edition or a more advanced edition supports baseline instances. If your DataWorks service does not meet the requirements, you must upgrade it to Standard Edition or a more advanced edition first. For more information, see Differences among DataWorks editions.
Baseline instances are generated only for baselines that are enabled. For more information, see Manage baselines.
View baseline instances
Go to the Operation Center page.
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose . On the page that appears, select the desired workspace from the drop-down list and click Go to Operation Center.
In the left-side navigation pane of the Operation Center page, choose .
On the page that appears, click the Baseline Instances tab.
Area
Description
Filter
In the area marked with 1 in the preceding figure, you can specify the following filter conditions to search for the baseline instances that you want to view:
Data Timestamp, Owner, Event ID, Workspace, Baseline Name, Type, Priority, and Baseline Status.
List of baseline instances
In the area marked with 2 in the preceding figure, you can view the baseline instances that meet the specified filter conditions and view the following information about the baseline instances: Baseline Name, Owner, Workspace, Priority, Baseline Status, Completion Status, Time, Alert Contact, Margin Thres, Last Completed Instance Estimated, and Current Key Instance. In addition, you can click View Details, Handle, View Gantt Chart, or Related Events in the Actions column of a baseline instance to perform the related operation.
Baseline Status: the status of a baseline instance in a baseline. A baseline instance can be in one of the following states:
Normal: indicates that all the nodes associated with the baseline finish running before the alerting time.
Alerting: indicates that one or more nodes associated with the baseline are still running after the alerting time but before the committed time.
Overtime: indicates that one or more nodes associated with the baseline are still running after the committed time.
Others: indicates that all nodes associated with the baseline are suspended or no nodes are associated with the baseline.
Last Completed Instance Estimated: the node instance that is estimated to be the last one that finishes running in the baseline.
Current Key Instance: the first node instance that is not run as expected in the key path of the baseline. If an instance is not run as expected, the instance can be in one of the following states: Pending (Ancestor), Pending (Resource), Pending (Schedule), Running, and Failed.
Margin Thres: a certain amount of time reserved for O&M personnel to handle exceptions that occur on nodes in the baseline.
If a node in a baseline finishes running, the value of the Margin Thres parameter is calculated by using the following formula:
Margin Thres= Alerting time for the baseline - Actual completion time of the node in the baseline.If a node in a baseline does not finish running, the value of the Margin Thres parameter is calculated by using the following formula:
Margin Thres= Alerting time for the baseline - Estimated completion time of the node in the baseline.
If the value of the Margin Thres parameter is a negative value, the baseline enters the Alerting or Overtime state.
View the details of a baseline instance
To view the details of a baseline instance, find the baseline instance on the Baseline Instances tab and click View Details in the Actions column.
Basic Information: If you use an hour-level baseline, you can change the cycle of the baseline in the upper-right corner of the details page.
Committed Completion Time: the committed time before which all nodes in the baseline finish running (the latest time for data output).
Alerting Time: calculated by
subtracting the alert margin threshold from the committed completion time for the baseline.NoteIf you want to reserve a certain amount of time for O&M personnel to handle exceptions that occur on nodes in a baseline, you can specify an alert margin threshold for the baseline. The system uses the time obtained by
subtracting the alert margin threshold from the committed completion timeas the alerting time for the baseline. The alerting time is also the estimated time before which all nodes in the baseline finish running. For more information, see Core logic: baseline alert.Last Completed Instance Estimated: displays the node instance that is estimated to be the last one that finishes running in the baseline.
Current Key Instance: displays the first node instance that is not successfully run in the key path of the baseline. If an instance is not run as expected, the instance can be in one of the following states: Pending (Ancestor), Pending (Resource), Pending (Schedule), Running, and Failed.
Baseline Alert Handling: the person who handles the current baseline alert.
Key Path: displays the instances in the key path that prevents the nodes in the baseline from generating data. You can view the instances in list or Gantt chart mode. For more information about how to identify a key path, see Core logic: key path and key instance.
NoteThe Gantt chart displays the status of nodes in the key path and the status of the nodes over a historical period of time.
History Curve: displays the completion status of nodes in the baseline over a historical period of time.
Related Events: displays the events that prevent nodes in the baseline from being complete on time. The event type can be Error or Slow. For more information, see Overview.