// Use this skill when working with Elastic SLOs (Service Level Objectives). Activate when the user asks about SLO status, burn rates, error budgets, or needs to create and manage SLO definitions.
Use when invoking the elastic CLI via elastic_cli or choosing CLI vs MCP/native Kibana tools. Covers shorthands, serverless gotchas, command names, and docs/ESQL flags.
Use this skill when writing or debugging ES|QL queries for Elasticsearch. Activate when the user asks to query logs, metrics, traces, or any Elasticsearch data using ES|QL syntax.
Use this skill when performing root cause analysis on incidents detected by Elastic Observability. Activate when the user reports a production issue, outage, degraded performance, or asks to investigate alerts.
| name | slo-management |
| description | Use this skill when working with Elastic SLOs (Service Level Objectives). Activate when the user asks about SLO status, burn rates, error budgets, or needs to create and manage SLO definitions. |
| metadata | {"version":"0.1.0","visibility":"public"} |
List all SLOs and their current status:
elastic slos list
List SLO definitions for configuration review:
elastic slos list-definitions
| Status | Meaning | Action |
|---|---|---|
| Healthy | Within error budget | No action needed |
| Degraded | Budget being consumed faster than expected | Monitor closely |
| Breached | Error budget exhausted | Immediate investigation required |
SLO data is stored in Elasticsearch indices. Query the rollup data:
elastic es query 'FROM .slo-observability.sli-v3* | STATS good = SUM(slo.numerator), total = SUM(slo.denominator) BY slo.id, slo.name | EVAL sli = good / total * 100 | SORT sli ASC | LIMIT 20'