datadog-query-recipes · git:20260928.90399fd · 2026-09-28 · sha256 cff025566cb2d5a5
datadog-query-recipes git:20260928.90399fdA
Immutable. This exact content never changes and is served at /api/v1/blob/cff025566cb2d5a5.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_sbodylybowfqakcj/cff025566cb2d5a5ee1e75cf8983cf5f984f7fb7ad10803713510a6272f5630a.json
Then /plugin install datadog-query-recipes@markdownregistry-sbodylybowfqakcj in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: datadog-query-recipes
description: |
Research Langfuse production telemetry with reusable Datadog queries. Use for
tenant or project activity, API usage, queue behavior, spans, logs, metrics,
or ad hoc measurements across production regions; pair with
debug-issue-with-datadog for root-cause analysis.
---
# Datadog Query Recipes
Use this skill for Langfuse production telemetry research where the main work is
finding the right Datadog data path. Keep findings evidence-based and include
the exact Datadog links or query shapes that support the answer.
## Required Scope
Unless the user explicitly narrows the scope, cover every production
environment:
- `prod-us`
- `prod-eu`
- `prod-hipaa`
- `prod-jp`
Query both Datadog sites when needed. Default to the EU site for `prod-eu` and
the US site for the other prod environments, but verify with a small count or
facet query before concluding an environment has no data.
Before querying live Datadog, load the relevant Datadog MCP guidance for the
data domain you need: traces, logs, metrics, and visualizations.
## Workflow
1. Identify the entity and signal: tenant ID, org ID, project ID, route, queue,
service, error class, or metric.
2. Read only the relevant reference:
- Prod environment/site routing:
[`references/environments.md`](references/environments.md)
- Public API tenant or legacy endpoint usage:
[`references/public-api-tenant-usage.md`](references/public-api-tenant-usage.md)
- Queue inventory, queue consumers, and queue metrics:
[`references/queue-consumers.md`](references/queue-consumers.md)
- Scheduled-export staleness (blob / PostHog / Mixpanel):
[`references/export-staleness.md`](references/export-staleness.md)
- Scheduled-export freshness lag (legacy per-run metric):
[`references/export-freshness-lag.md`](references/export-freshness-lag.md)
3. Start with aggregate queries, grouped by environment, service, route,
queue, project, org, status, or error facets as appropriate.
4. Fetch raw spans, logs, or traces only after aggregation identifies the
cluster or sample you need.
5. For tenant-specific HTTP usage, prefer trace correlation over single-span
queries when tenant tags and route tags live on different spans.
6. Report the windows, environments, sites, query links, and any sampling or
missing-data caveats.
## When To Use Other Skills
- Use [`debug-issue-with-datadog`](../debug-issue-with-datadog/SKILL.md) when a
Linear issue, GitHub issue, incident report, or monitor needs root-cause
analysis and patch recommendations.
- Use [`weekly-production-review`](../weekly-production-review/SKILL.md) when
the user asks for a weekly engineering overview of production bugs, pages,
and incidents.
- Use [`incident-alert-tickets`](../incident-alert-tickets/SKILL.md) when the
research is anchored to a named production alert or monitor: look up
documented causes before measuring, and record new ones only after human
approval.
- Use [`linear-bug-triage`](../linear-bug-triage/SKILL.md) only after a human
approves sharing measured findings in Linear.
## Output Expectations
Summarize what was checked, including:
- Datadog site and `env` values covered.
- Time windows.
- Core filters or metrics used.
- Count, rate, latency, queue depth, trace sample, or "No measurements found".
- Datadog links or trace IDs that let the human rerun the query.