What problem does it solve? Adding a Datadog monitor in this repository requires Terraform-only workflows, strict naming and tagging conventions, and query patterns that pass both terraform validate and Datadog's own validation — mistakes surface late in CI or break the release train. This Skill encodes all of those conventions so a new monitor is correct on the first commit. ## Core Features & Use Cases - Monitor Templates: Provides ready-to-adapt HCL patterns for log alerts, metric/query alerts, log-based metrics, synthetic HTTP checks, and composite API error-rate monitors. - Convention Enforcement: Covers naming with ${var.name_prefix}, Slack channel selection, recovery thresholds, traffic gates, and lifecycle rules like create_before_destroy for composite-referenced monitors. - CI Validation Guidance: Explains how terraform validate and terraform plan run in GitHub Actions, and how to pre-validate queries against /api/v1/monitor/validate. - Use Case: You need an alert when 5xx errors on a new API route exceed 10% with sufficient traffic. The Skill directs you to add a route entry to the api_error_rate module's route_groups list rather than writing a standalone monitor. ## Quick Start Add a Datadog log alert monitor for failed generation batch inserts using Terraform following the repo conventions.
