tempo-troubleshoot

帮助构建高效的Tempo跟踪查询,排查分布式跟踪问题,链接日志和指标(Loki/Mimir),并执行请求级别的根本原因分析。

📖 中文导读:帮助构建高效的Tempo跟踪查询,排查分布式跟踪问题,链接日志和指标(Loki/Mimir),并执行请求级别的根本原因分析。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

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

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.

  • 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