Tempo Troubleshoot

Help craft efficient Tempo trace queries, troubleshoot distributed traces, link logs and metrics (Loki/Mimir), and perform request-level root cause analysis.

majiayu000 Updated 567 repo stars

File contents

Tempo Distributed Tracing Troubleshooting Skill

What this Skill does

Use for:

  • TraceQL queries
  • Distributed tracing debugging
  • Correlating traces with logs & metrics
  • Investigating latency, errors, bottlenecks

Best Practices

Always start with service + time range

Examples:

  • resource.service.name = "payments"
  • span.status = "error"
  • span.duration > 500ms"

Avoid high-cardinality attributes

UUIDs, user IDs → only secondary filters.

Use TraceQL for structure

Preferring simple comparisons & attribute filters.

Link with Loki / Mimir when relevant

  • Loki: |= "<trace_id>"
  • Prometheus: find metrics for same window

Example Queries

Slow frontend traces

{ resource.service.name = "frontend" } | span.duration > 1s

Payment errors

{ resource.service.name = "payments", span.status = "error", start >= now() - 15m }

Limitations

  • Skill does not execute TraceQL

majiayu000/claude-skill-registry-data/tree/main/data/tempo-troubleshoot commit bfe24b0009

Frequently asked questions

npx skillmds@latest add majiayu000/tempo-troubleshoot