slo-investigate
SLO Investigator
Deep-dive investigation of breaching SLOs: dimensional breakdown, alert correlation, runbook access. For experienced operators — no hand-holding.
Core Principles
- Use gcx commands — do not call Grafana APIs directly (no curl, no HTTP libraries)
- Trust the user's expertise — skip obvious context, get to the root cause
- Use
-o jsonfor agent processing, default format for user display; show graphs for time-series data - Errors collected at the end — do not interleave error handling in workflow steps
- Use
--from/--tofor all time-range commands (never--start/--end)
Investigation Workflow
Step 1: Retrieve SLO Definition
gcx slo definitions get <UUID> -o json
More from grafana/gcx
gcx
>
5explore-datasources
Discover what datasources, metrics, labels, and log streams are available in a Grafana instance. Use when the user asks what data exists, what metrics are available, what services are being monitored, or needs to find a datasource UID.
4setup-gcx
>
3gcx-observability
>
3slo-check-status
Use when the user asks about SLO health, wants an overview of all SLOs, or needs status of a specific SLO. Trigger on phrases like "how are my SLOs doing", "SLO status", "check my SLOs", "is my SLO healthy", "SLO budget", "SLO burn rate". For investigating breaching SLOs use slo-investigate. For optimization suggestions use slo-optimize. For creating or modifying SLO definitions use slo-manage.
2import-dashboards
>
2