alerting-strategy
Alerting Strategy
Effective alerts that wake up on-call engineers only for real problems.
Context
You are designing alerts. Alert on SLOs, not absolute thresholds; provide runbooks.
Domain Context
- SLO: Service level objective; what level of service do you promise?
- Error Budget: How much downtime/errors before violating SLO?
- Alert Fatigue: Too many alerts → on-call ignores them
- Runbook: Step-by-step guide to respond to alert
- Escalation: If on-call doesn't respond, escalate
Instructions
- Define SLOs: What do you commit to? 99.9% uptime?
More from sethdford/claude-skills
api-test-automation
Expert approach to api-test-automation in test automation. Use when working with .
2developer-experience-audit
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
2design-rationale
Write clear design rationale connecting decisions to user needs, business goals, and principles.
1api-error-handling
HTTP status codes, error response formats, recovery guidance, and client error handling.
1interface-design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
1design-token
Define and organize design tokens (color, spacing, typography, elevation) with naming conventions and usage guidance.
1