metrics
Query timeseries data with PromQL, search metrics by name, list active metrics, or fetch metadata. Supports APM and percentile queries.
Instructions
Query Datadog metrics. Actions:
query: Get timeseries data (requires from/to time range, PromQL query)
search: Find metrics by name (grep-like, NO time param needed)
list: Get recently active metrics (last 24h, optionally filter by tag)
metadata: Get metric details (unit, type, description)
APM METRICS (auto-generated from traces): Keyed by OPERATION name (e.g. express.request, pg.query), NOT service name. Filter by service using tags: {service:my-service}
PERCENTILES (p50/p75/p90/p95/p99) — use the ROOT metric (distribution type): p95:trace.express.request{service:my-service}
AVG/SUM/MIN/MAX — use the .duration SUFFIX (pre-aggregated gauge): avg:trace.express.request.duration{service:my-service}
Other trace metrics (gauges):
trace..hits - Request count
trace..errors - Error count
trace..apdex - Apdex score
To discover operation names for a service, use: traces tool with action "services"
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | Action to perform | |
| query | No | For query: PromQL expression (e.g., "avg:system.cpu.user{*}"). For search: grep-like filter on metric names. For list: tag filter. | |
| from | No | Start time (ONLY for query action). Formats: ISO 8601, relative (30s, 15m, 2h, 7d), precise (3d@11:45:23) | |
| to | No | End time (ONLY for query action). Same formats as "from". | |
| metric | No | Metric name (for metadata action) | |
| tag | No | Filter by tag | |
| limit | No | Maximum number of results (for search/list, default: 50) | |
| pointLimit | No | Maximum data points per timeseries (for query action). AI controls resolution vs token usage (default: 1000). |