Batch Runs tab

The Batch Runs tab shows all of the current and historical runs for the batch pipeline components in a project.

Tip

Terms review: a run is a single execution of a batch pipeline. A batch pipeline is a type of Observability component. A run consists of a series of events that Observability receives and aggregates using event-specific metadata such as keys.

Run data

By default, the list is sorted by start time, from most recent to oldest.

Records include a run key, information about the component where the run took place, run timings, and statuses, where available.

• The Run Key column displays a unique identifier that associates the event data to a run.
• The Batch Pipeline column shows the component that the run is associated with.
• Start and end times use the time received if no timestamp is sent with an event.
• When an expectation is set, any Pending or Missing runs display with the time the run should have occurred in grey.
• The Duration column shows the total length of time for completed runs and the time elapsed for runs in progress.
• The Run Status column shows the status for each run.
• When tasks and tests are included in a run, the Tasks status column shows a summary of their statuses.
  • Hover your cursor to display an itemized list with more details.

Drill down

• Use the Date range, Tools, Components, or Statuses filters to narrow your results.
• Hover your cursor over truncated run keys and batch pipeline names to display the information in full.
• Hover your cursor over lateness indicators to see whether the run started or ended later than your expectation.
• Click a run key to open the details for a run.
• Use Refresh to update the page with new runs.
• Click Show/Hide Columns to customize the table.
  • If a run_name is sent with your events, select name to add the Run Name column to the table.

Visual example in Observability