dt-obs-tracing

Analyze and visualize distributed traces and service dependencies in Dynatrace using DQL queries.

2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/pvellido1/traces-flow --skill dt-obs-tracing-pvellido1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-obs-tracing
Source: https://github.com/pvellido1/traces-flow/tree/main/.github/skills/dt-obs-tracing
Command: npx skills add https://github.com/pvellido1/traces-flow --skill dt-obs-tracing-pvellido1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users analyze and visualize distributed traces, spans, and service dependencies in Dynatrace, providing insights into performance, failure detection, and service communication.

Core Features & Use Cases

  • Distributed Trace Analysis: Query and analyze trace data, explore request flows, and investigate span-level details.
  • Service Performance: Analyze service performance with error rates, response time percentiles, and slow trace detection.
  • Service Dependencies: Analyze incoming and outgoing service communication, identify external API dependencies.
  • Trace Aggregation: Aggregate all spans in a trace to understand full request flow and identify multi-service traces.
  • Request-Level Analysis: Access custom request attributes, capture attributes from method parameters, and aggregate spans by request ID.
  • Span Types: Analyze HTTP, database, messaging, RPC, and serverless spans, including latency, error rates, and failure patterns.
  • Advanced Topics: Exception analysis, logs and traces correlation, network analysis, and performance optimization techniques.
  • Use Case: Suppose you have a complex microservices architecture with performance issues. Use this Skill to identify slow or failing services, investigate root causes, and optimize service communication.

Quick Start

Use the dt-obs-tracing skill to fetch spans related to the 'serviceA' service with the HTTP method 'GET'.

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 and spans in Dynatrace?

To analyze distributed traces in Dynatrace, use DQL queries to fetch spans, explore request flows, and investigate span-level details for performance and failure detection. This allows you to map out service dependencies and identify slow requests.

How can I identify slow or failing services in a microservices architecture?

You can identify slow or failing services by analyzing service performance metrics like error rates and response time percentiles. Aggregating spans in a trace helps detect slow traces and pinpoint failing services within your architecture.

Can I correlate logs with distributed traces in Dynatrace?

Yes, you can perform logs and traces correlation in Dynatrace to investigate root causes. By querying span data alongside logs, you can analyze exceptions and understand the exact context of failures during request processing.

Do I need to know DQL to analyze service dependencies and request flows?

Yes, understanding DQL is required to analyze service dependencies and request flows. You need access to a Dynatrace environment to execute DQL queries for fetching and aggregating spans by request ID or service.

What span types are supported for latency and failure pattern analysis?

Supported span types include HTTP, database, messaging, RPC, and serverless spans. You can analyze each type to measure latency, calculate error rates, and detect specific failure patterns within your service communication.