Get Cluster Event

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.

Path Parameters
event_id string — REQUIRED Cluster monitor event identifier or latest

Query Parameters
selector string Possible values: [all, status] 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.

Responses
200 Schema — OPTIONAL all_healthy boolean api_resources_info string — OPTIONAL api_self_info string — OPTIONAL api_status string Possible values: [InitialUnhealthy, Unhealthy, Healthy] compiler_resources_info string — OPTIONAL compiler_self_info string — OPTIONAL compiler_status string Possible values: [InitialUnhealthy, Unhealthy, Healthy] id uuid Cluster monitor event identifier. recorded_at date-time runner_resources_info string — OPTIONAL runner_self_info string — OPTIONAL runner_status string Possible values: [InitialUnhealthy, Unhealthy, Healthy]
404 Schema — OPTIONAL details object Detailed error metadata. The contents of this field is determined by error_code. error_code string Error code is a string that specifies this error type. message string Human-readable error message.
500 Schema — OPTIONAL details object Detailed error metadata. The contents of this field is determined by error_code. error_code string Error code is a string that specifies this error type. message string Human-readable error message.
501 Schema — OPTIONAL details object Detailed error metadata. The contents of this field is determined by error_code. error_code string Error code is a string that specifies this error type. message string Human-readable error message.