dt-obs-tracing

Name: dt-obs-tracing
Availability: InStock
Author: mf-dynatrace

Analyze distributed traces and service dependencies using Dynatrace DQL queries.

Updated Jun 18, 2026

Search Tags:#distributed tracing #request analysis #exception analysis #span analysis #service dependency

Ready to run

npx skills add https://github.com/mf-dynatrace/dt-mcp-workspace --skill dt-obs-tracing-mf-dynatrace

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you investigate and analyze distributed traces, spans, and service dependencies to diagnose issues, understand performance bottlenecks, and optimize your applications.

Core Features & Use Cases

Trace Analysis: Investigate span-level details, failures, and performance bottlenecks.
Service Dependency Mapping: Understand service-to-service communication patterns and external API calls.
Request-Level Analysis: Analyze performance, failures, and dependencies at the request level.
Span Type Analysis: Analyze different types of spans like HTTP, Database, Messaging, and RPC.
Exception Analysis: Investigate exceptions in your application.

Quick Start

Run the 'analyze-trace' command to analyze a specific trace.

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 diagnose application performance bottlenecks?▼

This Skill analyzes distributed traces by investigating span-level details and failures, allowing you to diagnose performance bottlenecks and understand service-to-service communication patterns.

Can I analyze service dependencies and external API calls from distributed traces?▼

Yes, service dependency mapping is supported. You can analyze distributed traces to understand service-to-service communication patterns and trace external API calls for diagnostic insights.

How do I investigate exceptions and failures within specific span types?▼

You can investigate exceptions by analyzing distributed traces that support various span types, including HTTP, Database, Messaging, and RPC, to isolate failures and diagnose application issues.

Do I need Dynatrace data and DQL queries to perform request-level analysis?▼

Yes, performing request-level analysis requires access to Dynatrace data and DQL queries to evaluate performance, analyze failures, and map dependencies accurately across your services.

What is the best way to map service dependencies for diagnosing application issues?▼

Analyzing distributed traces and spans is the best way to map service dependencies, providing insights into service-to-service communication patterns and external calls to diagnose application issues.