observability-service-reliability

Design and operate service reliability targets in Elastic Observability: choose an SLI type and a defensible target, pick a time window and budgeting method, create and maintain SLOs through the Kibana API, attach burn-rate alert rules, and decide when an SLO is the wrong instrument and a threshold rule, anomaly job, or synthetics monitor is right. Use when defining or reviewing SLOs and error budgets, tuning burn-rate alerting, reducing alert noise, or setting up availability monitoring for a user-facing endpoint.

Version

0.4.1

Compatibility

Requires Kibana 8.x or 9.x with a matching Elasticsearch cluster (self-managed, Elastic Cloud Hosted, or Serverless) and the Observability solution enabled. The cluster must have nodes carrying both the `transform` and `ingest` roles, since every SLO is backed by a continuous transform. Needs the `elastic` CLI >= 0.2 with `stack kb` and `stack es` support. Synthetics SLIs additionally require the Synthetics app and at least one configured monitor location.