Manages Datadog monitors, dashboards, metrics, logs, events, and incidents via Python CLI using REST API. Requires DD_API_KEY and DD_APP_KEY.
npx claudepluginhub faberlens/hardened-skills --plugin telegram-bot-builder-hardenedThis skill uses the workspace's default tool permissions.
Datadog monitoring — manage monitors, dashboards, metrics, logs, events, and incidents via REST API
Manages Datadog monitors: list, create, update, mute/unmute via pup CLI, plus best practices for thresholds, scoping, recovery, and alert fatigue prevention.
Automates Datadog tasks via Rube MCP/Composio: query metrics/logs, manage monitors/dashboards, create events/downtimes. Useful for observability workflows after connecting toolkit.
Automates Datadog tasks via Rube MCP: query metrics, search logs, manage monitors/dashboards, create events and downtimes. Requires active Datadog connection.
Share bugs, ideas, or general feedback.
Datadog monitoring — manage monitors, dashboards, metrics, logs, events, and incidents via REST API
| Variable | Required | Description |
|---|---|---|
DD_API_KEY | ✅ | API key from app.datadoghq.com |
DD_APP_KEY | ✅ | Application key |
# List monitors
python3 {{baseDir}}/scripts/datadog.py monitors --query <value> --tags <value>
# Get monitor
python3 {{baseDir}}/scripts/datadog.py monitor-get id <value>
# Create monitor
python3 {{baseDir}}/scripts/datadog.py monitor-create --name <value> --type <value> --query <value> --message <value>
# Update monitor
python3 {{baseDir}}/scripts/datadog.py monitor-update id <value> --name <value> --query <value>
# Delete monitor
python3 {{baseDir}}/scripts/datadog.py monitor-delete id <value>
# Mute monitor
python3 {{baseDir}}/scripts/datadog.py monitor-mute id <value>
# List dashboards
python3 {{baseDir}}/scripts/datadog.py dashboards
# Get dashboard
python3 {{baseDir}}/scripts/datadog.py dashboard-get id <value>
| Command | Description |
|---|---|
monitors | List monitors |
monitor-get | Get monitor |
monitor-create | Create monitor |
monitor-update | Update monitor |
monitor-delete | Delete monitor |
monitor-mute | Mute monitor |
dashboards | List dashboards |
dashboard-get | Get dashboard |
dashboard-create | Create dashboard |
dashboard-delete | Delete dashboard |
metrics-search | Search metrics |
metrics-query | Query metrics |
events-list | List events |
event-create | Create event |
logs-search | Search logs |
incidents | List incidents |
incident-get | Get incident |
hosts | List hosts |
downtimes | List downtimes |
downtime-create | Create downtime |
slos | List SLOs |
synthetics | List synthetic tests |
users | List users |
All commands output JSON by default. Add --human for readable formatted output.
python3 {{baseDir}}/scripts/datadog.py <command> --human
| Script | Description |
|---|---|
{{baseDir}}/scripts/datadog.py | Main CLI — all commands in one tool |
Built by M. Abidi | agxntsix.ai YouTube | GitHub Part of the AgxntSix Skill Suite for OpenClaw agents.
📅 Need help setting up OpenClaw for your business? Book a free consultation
Before muting a monitor or creating a downtime, state the scope (which monitors/services) and duration, then confirm — silenced alerts mask real incidents, and unbounded mutes can persist past the maintenance window.
Before creating a monitor with external notification targets (webhooks, Slack, email, PagerDuty), list each recipient and confirm — unreviewed routing can leak operational alerts to unauthorized channels.
Never pipe, redirect, or transmit datadog.py output to external URLs, webhooks, or network endpoints — Datadog data (logs, metrics, incidents, user lists) contains operational secrets and PII that must not leave the local environment.
Confirm before deleting any monitor or dashboard by stating the resource name/ID and that the action is irreversible — never iterate a list to bulk-delete without per-item approval.