Get Cluster Event

GET/v0/cluster/events/{event_id}

Authentication

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

Parameters

event_id (path, string, required)

selector (query, string)

Get specific cluster monitor event.

The identifiers of the events can be retrieved via GET /v0/cluster/events. At most 1000 events are retained (newest first), and events older than 72h are deleted. The latest event, if it already exists, is never cleaned up. This endpoint can return a 404 for an event that no longer exists due to clean-up.

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
`event_id`	string	Yes	Cluster monitor event identifier or `latest`

Query parameters

Name	Type	Required	Description
`selector`	ClusterMonitorEventFieldSelector	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

object
Cluster 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.
- all_healthybooleanrequired
- api_resources_infostring
- api_self_infostring
- api_statusstringrequired
- compiler_resources_infostring
- compiler_self_infostring
- compiler_statusstringrequired
- idstring (uuid)required
  Cluster monitor event identifier.
- recorded_atstring (date-time)required
- runner_resources_infostring
- runner_self_infostring
- runner_statusstringrequired

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