
Dd Monitors
This handles Datadog monitor management through the command line, letting you list, search, create from files, and manage alerting downtimes. What makes it worth looking at is the opinionated best practices baked in: it pushes you toward stable alert windows, proper recovery thresholds to prevent flapping, and a safe deletion workflow that marks monitors instead of nuking them. The guidance on avoiding alert fatigue is solid, like using 5 minute windows instead of 1 minute, scoping alerts to what actually matters, and including runbooks in messages. Requires pup in your path to work with the Datadog API.
- skills.sh installs
- 2K
- GitHub stars
- 184
- last updated
- Aug 21, 2026
Install
$ npx -y skills add datadog-labs/agent-skills --skill dd-monitors --agent claude-codeInstalls into .claude/skills of the current project.
Files
Datadog Monitors
Create, manage, and maintain monitors for alerting.
Prerequisites
This requires pup in your path. See Setup Pup.
Command Execution Order (Token-Efficient)
For scoped commands, use this order:
- Check context first (prior outputs, conversation, saved values).
- If a required value is missing, run a discovery command first.
- If still ambiguous, ask the user to confirm.
- Then run the target command.
- Avoid speculative commands likely to fail.
Quick Start
pup auth login
Common Operations
List Monitors
pup monitors list
pup monitors list --tags "team:platform"
Get Monitor
pup monitors get <id>
Create Monitor
pup monitors create --file monitor.json
Silence Alerts (Downtime)
# No pup monitors mute/unmute commands.
# Use downtime payloads to silence monitor notifications.
pup downtime create --file downtime.json
pup downtime cancel <downtime_id>
Monitor Creation Best Practices
1. Avoid Alert Fatigue
Sponsors
Details
- Repository
- github.com/datadog-labs/agent-skills
- Categories
- DevOps & CI/CD, AI & Agent Building
- First seen
- May 16, 2026