alerting-standards

What problem does it solve?

This Skill establishes clear guidelines for creating effective alerts, ensuring that critical application failures are immediately noticed and addressed by the right teams, preventing silent outages and data loss.

Core Features & Use Cases

• Defines Alerting Principles: Emphasizes alerting on failures, providing context, avoiding fatigue, and centralizing notifications.
• Severity Levels: Clearly categorizes alerts into critical, high, and warning with corresponding response expectations.
• Contextual Alerts: Mandates essential fields like severity, service, environment, message, timestamp, and context for actionable alerts.
• Backend & Frontend Guidance: Provides specific patterns for implementing alerts in backend services and advises against direct alerting from frontend applications.
• Integration with Logging: Highlights the complementary relationship between logging and alerting.
• Use Case: When a critical payment processing failure occurs, this skill ensures an alert is sent with all necessary details (like affected endpoint and error count) to the operations team, along with a pointer to the relevant logs for immediate investigation.

Quick Start

Apply the alerting standards to ensure fatal errors trigger alerts that reach operations teams.