skills.rest
titaneric
titanericCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

slo-check-status

Checks SLO health, error budget consumption, and burn rate trends via gcx commands.

1|Updated May 25, 2020
Search Tags:#monitoring#grafana#sre#error budget#slo#burn rate#gcx
One-click install
npx skills add https://github.com/titaneric/dotfiles --skill slo-check-status-titaneric
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: slo-check-status
Source: https://github.com/titaneric/dotfiles/tree/main/dot_agents/skills/slo-check-status
Command: npx skills add https://github.com/titaneric/dotfiles --skill slo-check-status-titaneric

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It gives SREs and platform engineers a fast, structured way to check the health of Service Level Objectives without manually querying Grafana APIs, surfacing SLI values, error budgets, and burn rates in one workflow. ## Core Features & Use Cases - SLO Overview: Lists all SLO definitions with status, SLI, and error budget using gcx slo definitions commands. - Timeline Graphs: Renders time-series SLI trends for any SLO over configurable windows such as 7d or 28d. - Status Interpretation & Routing: Explains OK, BREACHING, and NODATA states and routes breaching SLOs to investigation or optimization skills. - Use Case: When an on-call engineer asks "how are my SLOs doing", the skill lists all SLOs, flags any BREACHING ones, shows their timeline graphs, and suggests a deep-dive investigation. ## Quick Start Ask the assistant to show the current status and error budget of all your SLOs.

Frequently Asked Questions about slo-check-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the status of all my SLOs at once?▼

Run gcx slo definitions status to get a table of every SLO with its SLI, error budget, and health status. Combine it with gcx slo definitions list to see UUIDs, objectives, and windows for each SLO.

How do I view SLO burn rate and SLI trends over time?▼

Use gcx slo definitions timeline with a time range such as --from now-7d --to now or --since 7d. The command renders a graph by default, and for a specific SLO you can pass its UUID; -o wide on the status command also shows BURN_RATE, SLI_1H, and SLI_1D.

What does NODATA status mean for an SLO?▼

NODATA means no Prometheus metrics are arriving from the SLO's recording rules. This usually indicates the destination datasource is misconfigured or the recording rules are not evaluating, so check the datasource configured on the SLO definition.

What should I do when an SLO is BREACHING?▼

A BREACHING status means the SLI is below the objective and error budget is being consumed. Review the timeline graph for the affected window, then use the slo-investigate skill for raw metrics, dimensional breakdown, and alert rule analysis.

Why does gcx return authentication errors when checking SLOs?▼

Auth errors mean the gcx context is missing a valid server URL or credentials. Run gcx config view to inspect the current context configuration and confirm the server and credentials are set correctly.

Related Skills

Explore More Software Engineering Skills→
opensearch-projectopensearch-project
34

slo-sli

Automate SLO/SLI definitions and burn-rate alerting with Prometheus recording rules.

Official
Advanced
grafanagrafana
535

slo-investigate

Correlate SLO definitions with metrics, alerts, and runbooks to diagnose breaches.

Official
Advanced
TravisLeeeeeeTravisLeeeeee
110

SRE (Site Reliability Engineer)

Define SLOs, multi-window burn-rate alerts, and observability plans for production microservices.

Community
Advanced
vibercoder79vibercoder79
8

grafana

Generate and update Grafana Cloud dashboards, panels, and PromQL alert rules.

Community
Intermediate