skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / DevOps / Sre Dashboards Skill by @BagelHole
The skill is the devops/observability/sre-dashboards folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Design and operationalize SRE dashboards that surface reliability, latency, error, saturation, and capacity signals across services.
Designs dashboards around reliability: the golden signals of latency, errors, traffic and saturation, plus SLO panels and capacity views, aimed at incident response and observability reviews.
The original SKILL.md is organised into these sections:
Written and maintained by @BagelHole. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
# SRE Dashboards Build dashboards that help teams detect, triage, and prevent reliability incidents. ## When to Use This Skill Use this skill when: - Defining service-level dashboards for production systems - Tracking SLO health and error-budget burn - Creating incident command-center views - Standardizing dashboard patterns across teams ## Prerequisites - Metrics pipeline (Prometheus, OpenTelemetry, or vendor equivalent) - Logs/traces linked to services and environments - Agreed service taxonomy (team, service, tier, environment) ## Dashboard Architecture Structure dashboards in layers: 1. **Executive Reliability View**: SLO attainment, incident counts, MTTR trends. 2. **Service Health View**: RED/USE metrics, dependency health, release markers. 3. **Deep-Dive View**: Per-endpoint latency, resource saturation, error categories. Keep each view answer-oriented: - *Are customers impacted?* - *What changed?* - *Where is the bottleneck?* ## Core SRE Panels ### Golden Signals …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.