[SLO] SLO ops management page

🍒 Summary

The SLO ops management page would provide a single pane of glass for users to manage all their SLOs and get insight into potential issues with the underlying infrastructure powering the SLOs, e.g. pipeline and transforms. This page would focus on the SLO definitions instead of the SLO instances as the current SLO listing page is showing.

Available bulk actions:

Bulk delete SLO
Bulk reset SLO
Bulk delete stale SLO instances

The page lists the SLO definitions including:

SLO name
Status
Number of instances
Other?

Misc:

Pagination
Searching by slo.name
Searching by slo.id
Filter by status
Sorting by number of instances

Status field

[!NOTE]
This field provides the overall SLO health status from an operational standpoint. If possible this should be a red-yellow-green light.

This field is computed using the following checks:

SLO Version Model is up to date
Both transforms exist and are healthy
Both ingest pipelines exist
Duration between last sli @timestamp and its event.ingested is within reason

APIs

[!NOTE]
Some existing APIs might be reusable.

List SLO definitions

The current GET /_definitions routes uses the SLO Repository directly. On this Ops page, we need to be able to filter by the Ops Status, which requires us to start from the summary index and then merge the result with the SLO Definition retrieved from the SLO Repository.

elastic / kibana