slo-check-status
SLO Status Checker
Check SLO health, budget consumption, and trends. Route to investigation or optimization as needed.
Core Principles
- Use
gcxcommands — do not call Grafana APIs directly - Trust the user's expertise — no hand-holding or excessive explanation
- Use
-o jsonfor agent processing, default format for user display - Show graphs for time-series data (timeline commands default to graph output)
Workflow
Step 1: Overview or Specific SLO
If the user asks about all SLOs (no specific UUID):
gcx slo definitions list
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-investigate
Use when a specific SLO is breaching or alerting and the user needs to understand why — root cause analysis, dimensional breakdown, alert rule correlation, runbook access. Trigger on phrases like "investigate SLO", "why is my SLO breaching", "SLO error budget burning", "SLO alerting". For SLO status overview use slo-check-status. For creating or modifying SLOs use slo-manage. For optimization suggestions use slo-optimize.
2import-dashboards
>
2