dt-obs-tracing

Query Dynatrace distributed traces and spans with DQL.

2|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/israel-salgado/dt-mcp-server --skill dt-obs-tracing-israel-salgado
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-obs-tracing
Source: https://github.com/israel-salgado/dt-mcp-server/tree/main/.agents/skills/dt-obs-tracing
Command: npx skills add https://github.com/israel-salgado/dt-mcp-server --skill dt-obs-tracing-israel-salgado

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyze distributed traces and spans in Dynatrace to understand end-to-end request flows and performance.

Core Features & Use Cases

  • Trace fundamentals: spans, root spans, and service context enrichment for dashboards and reports.
  • Patterned queries: end-to-end trace analysis, service dependency mapping, performance hotspots, and failure investigation.
  • Use cases: root-cause analysis, latency breakdown by endpoint/service, and exemplar traces for drill-down.

Quick Start

Analyze a trace by fetching its spans with DQL and inspect the root span and per-service timings.

Frequently Asked Questions about dt-obs-tracing

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

FAQPage Schema
How do I query distributed traces in Dynatrace to understand end-to-end request flows?

Query distributed traces in Dynatrace by fetching spans with Dynatrace Query Language (DQL). This identifies the root span and per-service timings to map end-to-end request flows and dependencies across your services.

What is the best way to perform root-cause analysis using Dynatrace spans and DQL?

Perform root-cause analysis by querying Dynatrace spans with DQL to filter for errors and failures. You can isolate problematic service-level aggregations, inspect trace exemplars, and map dependencies to pinpoint the exact failure source.

Can I map service dependencies and performance hotspots using Dynatrace DQL?

Yes, map service dependencies and performance hotspots using Dynatrace DQL. Query distributed traces to aggregate service-level timings, identify latency breakdowns by endpoint, and highlight performance bottlenecks across the request flow.

How do I identify the root span and per-service timings when analyzing a Dynatrace trace?

Identify the root span and per-service timings by fetching all spans within a Dynatrace trace using DQL. Enrich the spans with service context to inspect individual service durations and map the complete request flow.

Does this approach support investigating failures and error traces using Dynatrace Query Language?

Yes, this approach supports failure investigation using Dynatrace Query Language. You can query error and failure analyses within spans, drill down into trace exemplars, and isolate the failing services within your distributed architecture.