observability-sre-triage

Triage a degraded or suspect service end to end: read SLO status and burn rate, check active alerting rules and ML anomalies, measure throughput, latency, and error rate, assess dependency health and infrastructure saturation, and funnel logs down to the failures that explain it. Use when someone asks whether a service is healthy, why it is slow or erroring, what is in its logs, or which attribute distinguishes the requests that are failing. Also use when someone asks for the query behind any of those signals — throughput, latency percentiles, error rate, dependency health, or log volume — over APM/OTel traces, metrics, or logs.

Version

0.5.1

Compatibility

Requires the `elastic` CLI (>= 0.2) with Elasticsearch and Kibana contexts on the same cluster. Base floor is Elasticsearch 8.11+ or Serverless. Three ES|QL features need more, each with a fallback at its point of use: `FORK` (Stack GA 9.4), `CATEGORIZE` (Stack GA 9.1, Platinum licence) and `TS` (Stack GA 9.4); all are GA on Serverless. Reads APM/OTel traces, metrics and logs, the Kibana SLO and Alerting APIs, and the Elasticsearch ML APIs. Read-only.