site-reliability-engineer

SLOs (Service Level Objectives) and SLIs (Service Level Indicators) measure reliability by tracking specific metrics like uptime or latency against targets. Define SLIs based on what matters to users, then set SLOs as achievable thresholds—for example, 99.9% availability. This Skill provides templates to define and track these for your distributed systems.

Configure Prometheus to scrape metrics from your services, then visualize them in Grafana dashboards to track performance. This Skill covers monitoring stack setup, dashboard creation, and metric configuration across cloud-native services to establish observability from the start.

Alert rules trigger when metrics breach thresholds, enabling rapid incident detection. This Skill provides templates for setting alert rules across monitoring stacks like Prometheus, Datadog, and New Relic, helping you define conditions that catch production issues early.

Yes. This Skill includes incident response workflows, on-call readiness procedures, and runbook templates to guide teams through detection, mitigation, and resolution of production issues in distributed systems.

Health checks verify service availability in real time; error budgets quantify acceptable downtime against your SLO. Together, they balance reliability investment with feature velocity. This Skill configures both to maintain sustainable production operations.

Post-mortems document incidents without assigning blame, focusing on systems and processes. This Skill provides blameless post-mortem templates to capture what happened, why it happened, and what to improve—turning incidents into learning opportunities.