monitoring-alerting

Manage Datadog monitors, templates, notification routing, and downtimes via the pup CLI.

5|2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/lauhon/pi --skill monitoring-alerting-lauhon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-alerting
Source: https://github.com/lauhon/pi/tree/main/skills/monitoring-alerting
Command: npx skills add https://github.com/lauhon/pi --skill monitoring-alerting-lauhon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing Datadog monitoring at scale requires juggling monitors, reusable templates, alert routing rules, and maintenance windows across multiple APIs, which is error-prone and time-consuming when done manually. ## Core Features & Use Cases - Monitor Lifecycle Management: Create, list, search, update, and delete Datadog monitors of all types (metric, log, APM, composite) using the pup CLI. - Monitor Templates: Define reusable YAML templates with parameterized queries, thresholds, and notification channels, then apply them across services and environments. - Notification Routing: Configure rules that route alerts to Slack, PagerDuty, email, or webhooks based on tags, priority, severity, and time windows. - Downtimes: Schedule one-time or recurring maintenance windows to silence monitors during deployments or planned maintenance. - Use Case: When onboarding a new service, apply standard CPU, memory, and latency templates for each environment, create a routing rule sending production P0 alerts to PagerDuty, and schedule a weekly deployment downtime. ## Quick Start Ask the agent to list all currently alerting monitors in your production environment and show their details.

Frequently Asked Questions about monitoring-alerting

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

FAQPage Schema
How do I create a Datadog monitor from the command line?

Use the pup CLI to create monitors by specifying the monitor type, query, name, message, tags, and thresholds. You can also apply a reusable YAML template with pup monitor-templates apply and pass parameter values for service name, environment, and thresholds.

How do I route Datadog alerts to Slack or PagerDuty?

Create notification rules that match monitors by tags, name patterns, or alert states, then define targets such as Slack channels, PagerDuty service keys, email addresses, or webhooks. Rules support priorities, time-based conditions, aggregation, and throttling.

What environment variables does the pup CLI need for Datadog?

The pup CLI requires DD_API_KEY and DD_APP_KEY for authentication, plus DD_SITE which defaults to datadoghq.com. Template storage uses DD_TEMPLATES_DIR, defaulting to .datadog/templates/monitors.

How do I silence Datadog monitors during maintenance?

Create a downtime scoped by tags, monitor IDs, or monitor tags with a start and end time or duration. Recurring downtimes use RRULE syntax such as FREQ=WEEKLY;BYDAY=SA,SU for weekly weekend maintenance windows.

Why does monitor creation fail with a permission error?

Permission errors occur when the API and application keys lack required scopes such as monitors_read, monitors_write, or monitors_downtime. Verify your Datadog key scopes and confirm the monitor ID exists using pup monitors list.