Monitor management - list, search, file-based create, and alerting best practices.

Datadog Monitors Create, manage, and maintain monitors for alerting. Prerequisites This requires pup in your path. See [Setup Pup](https://github.com/datadog labs/agent skills/tree/main?tab=readme ov file setup pup). Command Execution Order (Token Efficient) For scoped commands, use this order: 1. Check context first (prior outputs, conversation, saved values). 2. If a required value is missing, run a discovery command first. 3. If still ambiguous, ask the user to confirm. 4. Then run the target command. 5. Avoid speculative commands likely to fail. Quick Start Common Operations List Monitors Get Monitor Create Monitor Silence Alerts (Downtime) Monitor Creation Best Practices 1. Avoid Alert Fatigue Rule Why No flapping alerts Use last Xm not last 1m Meaningful thresholds Based on SLOs, not guesses Actionable alerts If no action needed, don't alert Include runbook @runbook url in message 2. Use Proper Scoping 3. Set Recovery Thresholds 4. Include Context in Messages NEVER Delete Monitors Directly Use safe deletion workflow (same as dashboards): Monitor Types Type Use Case metric alert CPU, memory, custom metrics query alert Complex metric queries service check Agent check status event alert Event stream patterns log alert Log pattern matching composite Combine multiple monitors apm APM metrics Audit Monitors Downtime vs Muting Use When Downtime Any planned silence window Monitor edit Query/threshold behavior changes Failure Handling Problem Fix Alert not firing Check query returns data, thresholds Too many alerts Increase window, add recovery threshold No data alerts Check agent connectivity, metric exists Auth error pup auth refresh References [Monitor Types](https://docs.datadoghq.com/monitors/types/) [Alerting Best Practices](https://docs.datadoghq.com/monitors/guide/) [SLO Monitors](https://docs.datadoghq.com/service management/service level objectives/)

dd-monitors