Agent skill
tempo-troubleshoot
Help craft efficient Tempo trace queries, troubleshoot distributed traces, link logs and metrics (Loki/Mimir), and perform request-level root cause analysis.
Install this agent skill to your Project
npx add-skill https://github.com/timbuchinger/loadout/tree/main/skills/tempo-troubleshoot
SKILL.md
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
timbuchinger/loadout
brainstorming
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
timbuchinger/loadout
add-note
Use this skill whenever important information is learned during a task or when the user explicitly asks to store something. Use when users ask to remember. Triggers on "remember this", "update memory", "share" or any persistent storage request.
timbuchinger/loadout
user-story
Creates well-structured user stories for software development and project management. Use when the user asks to write, create, or format a user story, or needs to document requirements, features, or tasks in user story format.
timbuchinger/loadout
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
timbuchinger/loadout
kubernetes-troubleshoot
Troubleshoot and manage Kubernetes clusters, including resource inspection, debugging, pod logs, events, and cluster operations. Use when the user needs to diagnose issues, inspect workloads, analyze pod failures, or perform Kubernetes cluster operations.
timbuchinger/loadout
writing-plans
Use when design is complete and you need detailed implementation tasks - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming minimal codebase familiarity
Didn't find tool you were looking for?