dt-obs-tracing

Name: dt-obs-tracing
Availability: InStock
Author: Dynatrace

Analyze Dynatrace distributed traces with DQL to diagnose performance issues.

120|26|Updated Mar 31, 2026

Search Tags:#performance #observability #tracing #root-cause #spans #dql #dynatrace

Ready to run

npx skills add https://github.com/Dynatrace/dynatrace-for-ai --skill dt-obs-tracing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dt-obs-tracing
Source: https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-tracing
Command: npx skills add https://github.com/Dynatrace/dynatrace-for-ai --skill dt-obs-tracing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Dynatrace trace data across distributed services can be difficult to query and interpret; this skill provides ready-to-use patterns for investigating traces, spans, dependencies, and performance bottlenecks.

Core Features & Use Cases

Span-level tracing queries to inspect individual work units and their timing
Service dependency mapping to reveal call graphs and inter-service relationships
Failure investigation and performance analysis with root-cause patterns across traces

Quick Start

Load a sample trace and run a basic span query to identify slow endpoints.

Frequently Asked Questions about dt-obs-tracing

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

FAQPage Schema

How do I analyze distributed traces to find performance bottlenecks in microservices?▼

Service dependency mapping reveals call graphs and inter-service relationships by analyzing distributed traces. It traces end-to-end calls across multiple microservices, exposing the architectural flow and pinpointing where inter-service dependencies fail or introduce latency.

How do I investigate root-cause failures across Dynatrace spans?▼

Investigating root-cause failures across Dynatrace spans uses pattern-based queries to discover the originating span. By mapping service dependencies and analyzing the trace hierarchy, you isolate the failing microservice and diagnose the underlying issue causing the disruption.

What is the best way to query Dynatrace trace data for end-to-end troubleshooting?▼

The best way to query Dynatrace trace data for troubleshooting is using DQL patterns for root-span discovery. Ready-to-use query patterns allow you to inspect spans, map dependencies, and investigate failures without writing complex queries from scratch.

Do I need DQL to troubleshoot distributed tracing issues across microservices?▼

You need DQL to troubleshoot distributed tracing issues because the analysis relies on pattern-based investigations using Dynatrace Query Language. DQL queries enable span-level inspection, service dependency mapping, and root-cause analysis across end-to-end traces.