You can manage baseline instances on the Baseline Instance page.

Note
  • To use this feature, you must purchase DataWorks Standard Edition or a more advanced edition.
  • After a baseline is created, you must enable the baseline. This way, instances can be generated for the baseline.

On the Baseline Instance page, you can search for baseline instances based on the configurations of the Data Timestamp, Owner, Event ID, Workspace, Baseline Name, Recurrence, Priority, and Baseline Status parameters. You can click View Details, Handle, or View Gantt Chart in the Actions column that corresponds to a specific baseline instance to perform the related operation.

You can filter baseline instances based on the status by select one or more of the following options:
  • Normal: indicates that all the nodes associated with the baseline finish execution before the alerting time.
  • Alerting: indicates that one or more nodes associated with the baseline do not finish execution after the alerting time but before the committed time.
  • Overtime: indicates that one or more nodes associated with the baseline do not finish execution after the committed time.
  • Others: indicates that all nodes in the baseline are paused or the baseline is not associated with any node.

You can click View Details, Handle, or View Gantt Chart in the Actions column as required.

  • View Details: Click View Details to view the details about the baseline instance in the Baseline Instance Details dialog box. View Details

    In the Baseline Instance Details dialog box, you can view the information in the following sections: General, Critical Path, Baseline Instance, History, and Events.

    Note
    • The data timestamp is one day earlier than the system date.
    • You can set the Cycle parameter only for hourly baselines.
  • Handle: Click Handle to handle the alert that is generated for the baseline instance. During this period, alerting is paused.
  • View Gantt Chart: Click View Gantt Chart to view the critical paths of the nodes that are associated with the baseline instance.

FAQ: Why is a baseline in the Empty Baseline state?

In the following scenarios, a baseline instance may be in the Empty Baseline state:

  • Scenario 1: A node can belong to only a baseline. When you add a node to another baseline, you actually move the node from the existing baseline to another one. If all nodes are removed from the existing baseline, the status of the existing baseline changes to Empty Baseline.
  • Scenario 2: On the day when a baseline is created, the baseline is in the Empty Baseline state. After you enable the baseline, a baseline instance is generated on the next day.
  • Scenario 3: You specify an invalid point in time for an auto triggered node instance in the hourly baseline.
    Note For example, you specify that the node is run at 6:00 and 18:00 every day. However, you specify that the baseline detects the node at 6:00 and 28:00.