mav-bp-alerting

Standardize fatal error alerting with severity levels and required context fields.

10|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/thermiteau/maverick --skill mav-bp-alerting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mav-bp-alerting
Source: https://github.com/thermiteau/maverick/tree/main/skills/mav-bp-alerting
Command: npx skills add https://github.com/thermiteau/maverick --skill mav-bp-alerting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Alerting conventions for fatal errors in applications ensures operators are notified with proper urgency and context, reducing mean time to recovery and alert fatigue.

Core Features & Use Cases

  • Centralized alerting guidance: defines severity levels, required fields, and response timelines.
  • Context-rich alerts: every alert includes service, environment, timestamp, and actionable context to accelerate investigation.
  • Project-wide enforcement: applies during error handling and code reviews to maintain consistency across services.

Quick Start

Configure your service to emit alerts following the mav-bp-alerting standards for a representative failure scenario.

Frequently Asked Questions about mav-bp-alerting

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

FAQPage Schema
How do I standardize fatal-error alerting across multiple services?

Reduce alert fatigue from fatal errors by enforcing deduplication, severity levels, and contextual requirements. This ensures operators receive timely, actionable notifications without being overwhelmed by redundant alerts.

What context fields should incident-management alerts include for production environments?

Incident-management alerts should include severity, service, environment, message, timestamp, context, and logPointer fields. These provide the actionable context needed to accelerate investigation and reduce mean time to recovery.

How do I set up centralized notifications for on-call error handling?

Set up centralized notifications by configuring your services to emit alerts with standardized severity levels and context fields, routing them to central notification channels for appropriate escalation across production, staging, and development environments.

Can I apply the same alerting severity levels across staging and development environments?

Yes, the alerting standards apply across production, staging, and development environments. Defining severity levels and response timelines ensures consistent error handling and escalation guidance regardless of the deployment target.

When should I not use centralized fatal-error alerting conventions?

Avoid centralized fatal-error alerting for non-fatal or expected operational warnings. The standards specifically target fatal errors requiring immediate on-call response, escalation, and deduplication to reduce alert fatigue.