← ClaudeAtlas

datadog-automationlisted

Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas.
aiskillstore/marketplace · ★ 334 · AI & Automation · score 83
Install: claude install-skill aiskillstore/marketplace
# Datadog Automation via Rube MCP Automate Datadog monitoring and observability operations through Composio's Datadog toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Datadog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `datadog` - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas ## Setup **Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `datadog` 3. If connection is not ACTIVE, follow the returned auth link to complete Datadog authentication 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Query and Explore Metrics **When to use**: User wants to query metric data or list available metrics **Tool sequence**: 1. `DATADOG_LIST_METRICS` - List available metric names [Optional] 2. `DATADOG_QUERY_METRICS` - Query metric time series data [Required] **Key parameters**: - `query`: Datadog metric query string (e.g., `avg:system.cpu.user{host:web01}`) - `from`: Start timestamp (Unix epoch seconds) - `to`: End timestamp (Unix epoch seconds) - `q`: Search string for listing metrics **Pitfalls**: - Query syntax follows Datadog's metric query format: `aggregation:metric_name{tag_filters}` - `from` and `to` are Unix epoch timestamps