datadog:traces

Search and analyze Datadog APM traces to identify errors and performance issues.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/fabn/claude-plugins --skill datadog-traces
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datadog:traces
Source: https://github.com/fabn/claude-plugins/tree/main/plugins/datadog/skills/traces
Command: npx skills add https://github.com/fabn/claude-plugins --skill datadog-traces

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Investigating APM traces in Datadog is time-consuming because raw trace responses are large, query syntax is non-intuitive, and single-trace lookups often require special sorting and time ranges to reveal root causes.

Core Features & Use Cases

  • Translate natural language intent into Datadog APM query syntax and build environment, service, status, endpoint, duration, and HTTP filters.
  • Support multiple modes: broad search of recent traces, direct trace ID or URL lookup with extended ranges, and code-driven query generation for endpoint-centric investigations.
  • Reduce huge trace payloads into concise structured summaries (endpoint, status, duration, error type, Datadog link) using a parse-traces.js helper to keep results small and actionable.
  • Use Case: Find slow 5xx requests for a production service, inspect the top spans for SQL queries, and provide direct Datadog links for drill-down.

Quick Start

Use the datadog:traces skill to find recent error traces for service my-app in the last hour and summarize the top results.

Frequently Asked Questions about datadog:traces

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search Datadog APM traces using natural language instead of query syntax?

Datadog APM traces can be searched by translating natural-language intent into query syntax, allowing you to filter by service, time range, status, endpoint, or duration without manual syntax construction.

What is the best way to find slow 5xx error traces for a production service?

Finding slow 5xx error traces involves executing a broad search with appropriate sorting and time ranges, then parsing the large trace responses into concise structured summaries to reveal endpoint, status, and error type.

How do I look up a single Datadog trace by ID or URL?

Single-trace lookups by ID or URL require executing list_traces with extended epoch-second time ranges and special sorting to ensure the specific trace is returned and its root cause is revealed.

Why does Datadog trace search return such large payloads and how can I reduce them?

Datadog trace search returns large payloads because raw trace responses contain extensive span data, which can be reduced into concise structured summaries using a parsing script to keep results actionable.

Can I filter Datadog APM traces by endpoint and duration without writing raw queries?

Filtering Datadog APM traces by endpoint and duration is supported through code-driven query generation, which translates your intent into environment, service, status, and HTTP filters automatically.