1. Habit
  2. Skills
  3. DT Obs Tracing skill
dynatrace · 3K installs

DT Obs Tracing skill
Runs by itself, every morning.

Slow and failed requests found daily.

Install the DT Obs Tracing skill and make it a habit: follow https://gethabit.dev/skills/dynatrace/dt-obs-tracing.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

3K installs166 starsApache-2.0 licenceSource on GitHub ↗

DT Obs Tracing

by dynatrace · 3K installs

The skill

The dt obs tracing skill analyses Dynatrace distributed traces and spans with DQL: slow requests, failed spans, failure reasons, service dependencies and exceptions, for SRE and backend teams.

Only when you ask.

The habit

Slow and failed requests found daily.

↻ Runs by itselfevery morning

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

every morning. Runs in Claude Code routine.

  • ↻ every morning
  • 0 8 * * *

02

It checks its work

query rules hold. If a check fails, it tries again.

  • ✓queries filter request.is_root_span == true
  • ✓every listed slow request has a trace.id
  • ✓operation counts use multiplicity extrapolation
  • ✓duration is compared as a DQL duration such as 5s

03

It remembers

endpoint latency log. The next run reads it first: p95 and p99 per endpoint from the last run.

loops/dynatrace-slow-trace-loop/log.md

One run, step by step.
Then it stops.

Stop ruleStops after one report per run, with at most 50 slow traces listed.

  1. 01

    Find slow requests

    Your agent lists root spans with duration over 5s in the last two hours.

  2. 02

    Rank endpoints

    It computes p95 and p99 per endpoint.name.

  3. 03

    Summarise failures

    It computes failure rate per dt.service.name.

  4. 04

    Explain failures

    It breaks failures down by reason, such as http_code or exception.

  5. 05

    Attach exemplars

    It adds trace IDs with takeAny(record(start_time, trace.id)) for drilldown.

  6. 06

    Compare and log

    It compares percentiles with the last run and writes changes to the log.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the DT Obs Tracing skill helps.

Use it when

  • ✓ finding slow requests
  • ✓ analysing failed spans
  • ✓ mapping service dependencies

Skip it when

  • – log searching
  • – DAVIS problem analysis

Questions

DT Obs Tracing skill, answered.

Why extrapolate counts?

One span can stand for many operations because of sampling and aggregation.

What if root span filtering returns nothing?

For OpenTelemetry-only traces, the skill falls back to isNull(span.parent_id).

How do I install the DT Obs Tracing skill?

Copy the prompt at the top into your agent. It installs the skill from dynatrace/dynatrace-for-ai and sets up the habit. Or run npx skills add dynatrace/dynatrace-for-ai --skill dt-obs-tracing.

Is the DT Obs Tracing skill free?

Yes. It is published under Apache-2.0. Habit is free too.

DT Obs Tracing. Now as a habit.

Install the DT Obs Tracing skill and make it a habit: follow https://gethabit.dev/skills/dynatrace/dt-obs-tracing.md

  • Free
  • No account
  • Undo in one line

All dynatrace skills →More ops skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by dynatrace, published under Apache-2.0. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.