Back to Skills

dt-obs-tracing

Distributed traces, spans, service dependencies, and request flow analysis. Use when investigating span-level details, failures, performance bottlenecks, or trace correlation. Trigger: "trace analysis", "slow requests", "failed spans", "service dependencies", "distributed trace", "span details", "HTTP status codes in traces", "database query spans", "messaging spans", "gRPC calls", "Lambda cold starts", "trace ID lookup", "exception analysis", "correlate logs and traces", "request attributes". D

120stars26forksUpdated 8/13/2026

Security Assessment

Safe(95/100)
Security Score95/100

About dt-obs-tracing

dt-obs-tracing is an observability reference skill for analyzing distributed traces and spans in Dynatrace using DQL (Dynatrace Query Language) against Traces in Grail. It helps investigate span-level details, request failures, performance bottlenecks, and trace correlation, and is scoped to trace analysis specifically (deferring service RED metrics, log search, and problem analysis to sibling skills).

The skill explains trace fundamentals such as span kinds (server, client, consumer, producer, internal), root spans, and key attributes like trace.id, span.id, duration, and service identifiers, then supplies ready-to-run DQL query patterns for common use cases: finding slow requests over a latency threshold, analyzing failures by reason (HTTP code, gRPC status, exception, span status, custom rule), mapping service dependencies, and correlating logs with traces. Reference files go deep on span types (HTTP, RPC/gRPC, database, messaging, serverless), failure detection, exception and stack-trace analysis, request attributes, networking analysis, entity lookups, and sampling/extrapolation via adaptive traffic management. The queries are read-only fetch/filter/summarize/parse operations that report and aggregate telemetry.

It targets SREs, platform engineers, and developers who use Dynatrace and need to author trace queries to diagnose production issues. It is defensive, monitoring-oriented tooling that only reads and summarizes observability data; it contains no destructive operations, credential handling, or offensive capability.

FAQ

What query language does it use?

DQL (Dynatrace Query Language) against Traces in Grail, with fetch/filter/summarize/makeTimeseries/parse patterns provided for each analysis scenario.

What can I investigate with it?

Slow requests, request failures and their reasons, exception and stack-trace patterns, service dependencies, and correlation between logs and traces, plus span-type-specific analysis for HTTP, RPC/gRPC, database, messaging, and serverless spans.

When should I NOT use this skill?

For service-level RED metrics (use dt-obs-services), log searching (dt-obs-logs), problem analysis (dt-obs-problems), or general product documentation and configuration questions.

Does it modify anything in my environment?

No. The queries are read-only analysis over trace telemetry; they fetch, filter, aggregate, and parse spans rather than changing configuration or data.

Does it account for sampling?

Yes. It documents that one span can represent multiple real operations due to aggregation and adaptive traffic management (head-based sampling), and includes a reference on sampling and extrapolation.

All Files

13 files
references/failure-detection.md6.6 KB
View
references/messaging-spans.md3.6 KB
View
references/rpc-spans.md3.5 KB
View
references/database-spans.md4.2 KB
View
references/performance-analysis.md3.0 KB
View
references/serverless-spans.md4.1 KB
View
references/entity-lookups.md3.9 KB
View
references/logs-correlation.md3.7 KB
View
references/request-attributes.md4.6 KB
View
SKILL.md17.5 KB
View
references/http-spans.md4.7 KB
View
references/networking-analysis.md4.1 KB
View
references/sampling-extrapolation.md4.6 KB
View

Install dt-obs-tracing

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill