Runs¶
A run is a single execution of a batch pipeline. While a batch pipeline and its configuration reflect what is expected to happen, a run is what actually happens as events are received by the system.
Observability automatically creates a new run for a batch pipeline any time the system receives an event
with a run_key that does not match keys for that pipeline's existing runs.
Note
Send events with the run_name property to more easily identify runs occurring in your batch pipelines.
View batch pipeline runs¶
Observability data is always associated with a specific project.
- Use the drop-down in the menu to select a Project.
- Select Events from the menu.
-
Select the Batch Runs tab to see a list of all the runs.
See View Events and Runs for more details on the Batch Runs tab.
-
Click a Run Key to drill down into the details for a specific run.
For more information, see View Run Details.
Tip
The Batch Runs tab of the Events page displays all the runs in a given project. To see the runs associated with an instance, open the Batch Runs tab in the instance details.
Run data¶
Observability records the details of what happened during a batch pipeline execution and displays the following data:
- The run key (the unique identifier for the run) and name (if present in the event metadata).
- The batch pipeline component name.
- Status timings of the run.
- Results of timeliness and expectations.
- Status of its associated tasks and tests (if present).
Visual example in Observability¶
