List Pipeline Events

GET/v0/pipelines/{pipeline_name}/events

Authentication

JSON web token (JWT) or API key (http bearer)

Parameters

pipeline_name (path, string, required)

selector (query, string)

Retrieve monitoring events in reverse chronological order.

Pipeline health is monitored regularly every several seconds. Not every monitoring action results in a pipeline monitor event being constructed and inserted into the database. This happens if:

Any status changed
Only the status details changed, and it has been 10s since the last event
Nothing has changed for more than 10 minutes

This endpoint returns the most recent persisted events, up to by default approximately 720.

Authentication

Scheme	Type	Details
`JSON web token (JWT) or API key`	Bearer token	Authorization header · Use a JWT token obtained via an OAuth2/OIDC login workflow or an API key obtained via the `/v0/api-keys` endpoint.

Parameters

Path parameters

Name	Type	Required	Description
`pipeline_name`	string	Yes	Unique pipeline name

Query parameters

Name	Type	Required	Description
`selector`	PipelineMonitorEventFieldSelector	No	The `selector` parameter limits which fields are returned. Limiting which fields is particularly handy for instance when frequently monitoring over low bandwidth connections while being only interested in status.

Response

application/json

PipelineMonitorEventSelectedInfo[]
- object
  Pipeline monitor event information which has a selected subset of optional fields. If an optional field is not selected (i.e., is `None`), it will not be serialized.

curl -X GET '/v0/pipelines/{pipeline_name}/events?selector=%3Cselector%3E' \
  -H 'Authorization: Bearer YOUR_TOKEN'

[]