Dataphin:View and manage baseline instances

Area

Description

①Search and filter area

Search baseline instances by name or use quick filters: data timestamp, my owner, broken baseline, and incomplete baseline.

• Data Timestamp: Quickly filter baseline instances from yesterday.

• My Owner: Filter baseline instances where you are the owner.

• Broken Baseline: Filter baseline instances with a status of Broken.

• Incomplete Baseline: Filter baseline instances with a running status of Incomplete.

②Filter area

Click to expand the filter area:

• Baseline Status:

  • Safe: The baseline's (expected) completion time is on or before the alert time.

  • Alert: The baseline's (expected) completion time is after the alert time but on or before the commitment time.

  • Broken: The baseline's (expected) completion time exceeds the commitment time.

  • Others: All instances are paused or it's an empty baseline with no guaranteed nodes.

• Completion Status: Select Yes or No.

• Priority: Select Highest or High.

• Baseline Type: Select Daily Baseline or Empty Baseline.

  Note

  Empty baselines occur when all configured nodes are unpublished.

• Baseline Owner: Filter by baseline owner.

• Data Timestamp: Filter by data timestamp. Options: Today, Yesterday, and Custom Date.

③Baseline instance list

Displays baseline instance name, status, completion, alert/guarantee time, alert margin, latest instance, priority, type, owner, and available operations.

• Baseline instance details: Click the icon. view baseline instance details or .

• Critical path Gantt chart: Click the icon. view critical path Gantt chart or .

• Related alerts: Click the icon to view baseline instance related alerts. alert events.

Area

Description

Basic information

Includes baseline name, owner, priority, baseline type, guarantee time, and alert time.

(Expected) latest instance

The last node on the critical path.

Current Critical Instance

The highest instance on the critical path that has yet to run successfully.

Critical path

The longest path of guaranteed objects affecting the baseline. Shows the guarantee object name, details (logical table node), scheduled/expected output time, project/section, priority, and owner.

You can single click to view the critical path Gantt chart to open the critical path Gantt chart. view critical path Gantt chart or .

Historical running trends

Historical running trend chart.

• Horizontal axis: Data timestamp.

• Vertical axis: Output time.

• Data variables: Commitment time, alert time, average output time, and actual output time for each data timestamp, shown as lines and dots.

  • Commitment time: The deadline by which the baseline task must be successfully completed, indicated by a red dashed line () for clarity.

  • Alert time: is calculated as the committed time minus the alert buffer. It is indicated by an orange dashed line () on the chart.

  • Average production time: The average time of actual production on historical data timestamps. Marked with a green dashed line ().

  • Actual output time for each data timestamp: The specific time when the baseline task has been successfully executed, marked by a blue solid line ().

Alert events

A log of alert events triggered by the baseline instance, including alert node, reason, latest alert time, recipient, status, and actions.

• Alert node: Includes event and baseline alert nodes.

• Alert reason: Reasons such as baseline alert, broken baseline, task slowdown, or error.

• Latest alert time: The most recent time an alert was sent for an event.

• Recipient: The individual who received the alert.

• Operation: Click to go to the alert center.

Area

Description

①Basic information

Includes baseline name, owner, baseline status, commitment time, alert time, and slack.

You can set the time interval to 10 minutes or 30 minutes.

②Critical path Gantt chart

The chart includes the critical path node list and the progress time and status of each node within the current baseline instance.

• ①Node list order: Arranged from the start to the end of the critical path, top to bottom.

• ②Progress time: Shows the progress of nodes from the first successful upstream instance to the current status or waiting time.

• ③Historical average runtime and instance running status reversal time interval:

  • Historical average runtime: This displays the historical average runtime for the current instance node, serving as a benchmark to determine if the current runtime is abnormal. It is represented by light green bars () that denote the time interval. Hovering the mouse pointer over the mark reveals the recent average.

  • Instance running status reversal mark: Includes the time before all upstream runs are successful, the time from all upstream runs being successful to the scheduled time, the time from the scheduled time to the throttling pass time, the time from the throttling pass to the instance being issued to the compute engine runtime, and the time from operation pause to resume.

    • Time before all upstream runs are successful: The current instance node awaits the successful completion of all upstream instances on the critical path, with no specific task mark.

    • Time from all upstream runs being successful to the scheduled time: The upstream instances on the critical path have completed successfully, but the current business time has not reached the instance's scheduled time. This interval is indicated by a purple dashed line and a waiting time prompt () . Hover the mouse pointer over the mark to see the total duration.

    • Time from the scheduled time to the throttling pass time: Once the scheduled time is reached after all upstream instances have successfully run, this interval is marked with a purple dashed line and a waiting for issue prompt () . Hover the mouse pointer over the mark to view the total duration.

    • Time from the throttling pass to the instance being issued to the compute engine runtime: After the throttling pass is achieved post-scheduled time, this interval is denoted by green bars () . Hover the mouse pointer over the mark to view details such as the instance's Task ID, owner, project, running status, and duration.

    • Time from operation pause to resume: This marks the interval from the start of an operation pause to its resumption, indicated by a purple dashed line and a pause prompt () . Hover the mouse pointer over the mark to see the total duration.

      Important

      • If the instance node triggers a running slowdown alert, the system will highlight the corresponding time point with a yellow dot. Hover the mouse pointer over the mark to view the data timestamp, node name (node ID), reason, and occurrence time.

      • Should the instance node trigger a running slowdown alert, it will be marked with a red dot. Hover the mouse pointer over the mark to view the data timestamp, node name (node ID), reason, and occurrence time.

      • The alert time is indicated by a yellow solid line at the corresponding time point.

      • A red solid line marks the broken time at the corresponding time point.

      • When the alert time and broken time coincide, the alert time will be overwritten, and only the broken time will be indicated.