datadog-clilisted

# Datadog CLI Skill Use the instance and rules below when constructing all Datadog API commands. ## Configuration Update the table below with your Datadog site and credential file paths: | Environment | Site | API Key File | App Key File | |---|---|---|---| | Production | `<your-datadog-site>` (e.g. `datadoghq.com`, `datadoghq.eu`) | `~/.datadog/prod.api_key` | `~/.datadog/prod.app_key` | | Staging | `<your-datadog-site>` | `~/.datadog/staging.api_key` | `~/.datadog/staging.app_key` | If the target environment is unclear, ask the user before running any command. ## Prerequisites (one-time setup by user) Generate a Datadog API key and Application key for each environment (**Organization Settings → API Keys / Application Keys**) and save them to the corresponding files. Never print or display key values. Do not perform these steps yourself. ```bash mkdir -p ~/.datadog && echo "<your-api-key>" > <API_KEY_FILE> && echo "<your-app-key>" > <APP_KEY_FILE> && chmod 600 ~/.datadog/* ``` ## Command Format ```bash curl -s -H "DD-API-KEY: $(cat <API_KEY_FILE>)" \ -H "DD-APPLICATION-KEY: $(cat <APP_KEY_FILE>)" \ "https://api.<your-datadog-site>/api/<endpoint>" | jq . ``` ## Available API Endpoints ### Read-only (safe, no confirmation needed) | Endpoint | Method | Description | |---|---|---| | `/api/v1/query?query=<metric-query>&from=<ts>&to=<ts>` | GET | Query timeseries metrics | | `/api/v2/logs/events/search` | POST | Search log events | | `/api/v1/monitor` | GET | List