alerting-config

Design alert configurations with thresholds, severity, routing, and escalation policies.

22|8|Updated Mar 14, 2026

Search Tags:#devops #monitoring #infrastructure #alerting #alertmanager #pagerduty

Ready to run

npx skills add https://github.com/inbharatai/claude-skills --skill alerting-config

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: alerting-config
Source: https://github.com/inbharatai/claude-skills/tree/main/skills/alerting-config
Command: npx skills add https://github.com/inbharatai/claude-skills --skill alerting-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pagerduty, alertmanager.

What problem does it solve?

This Skill streamlines the creation and management of alert configurations, ensuring critical system events are detected and routed effectively.

Core Features & Use Cases

Threshold Definition: Set precise conditions for triggering alerts.
Severity Levels: Assign appropriate urgency to different types of alerts.
Routing & Escalation: Define how alerts are sent and who is notified.
De-duplication: Prevent alert storms by grouping similar events.
Use Case: Configure alerts for a web service, specifying that high-severity errors should immediately trigger an on-call engineer via PagerDuty, while low-severity warnings are logged and reviewed daily.

Quick Start

Help me design an alerting configuration for a critical database service with a severity level of 'critical' and route it to the 'oncall-db' channel.

Frequently Asked Questions about alerting-config

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

FAQPage Schema

How do I configure alerting thresholds and severity levels for infrastructure monitoring?▼

Alert routing and escalation policies define how alerts are sent and who is notified. You can configure high-severity errors to immediately trigger an on-call engineer via PagerDuty, while low-severity warnings are logged for daily review.

How do I prevent alert storms in Alertmanager?▼

To design alerting for a critical web service, specify that high-severity errors trigger immediate on-call engineer notification via PagerDuty, while low-severity warnings are logged and reviewed daily.

What's the best way to route critical alerts to an on-call engineer via PagerDuty?▼

To automate alerting operations, use the system to generate production-ready alerting configurations. This requires understanding PagerDuty and Alertmanager conventions to ensure proper routing and escalation.

Can I use Alertmanager with PagerDuty for escalation policies?▼

To automate alerting configuration generation, use the system to create production-ready configs with thresholds, severity levels, routing, and escalation policies. This requires understanding PagerDuty and Alertmanager conventions.

Why do I need de-duplication in my alerting configuration?▼

To configure web service alerting, specify that high-severity errors trigger immediate on-call engineer notification via PagerDuty, while low-severity warnings are logged and reviewed daily for trend analysis.

Does this alerting configuration support automation of operations?▼

To assign alert severity levels, define appropriate urgency for different alert types. High-severity errors trigger immediate on-call notification via PagerDuty, while low-severity warnings are logged and reviewed daily.