OpenParable
Skip to content
← Back to skills

Error Root Cause

Testing & Quality
error-root-cause

Error Root Cause is an Agent Skill for testing & quality published in the jaegertracing/jaeger repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Walk a failed trace to the first originating error span and distinguish root cause from cascading failures. Use when a trace has errors and the user asks why it failed, what caused the errors, or which service is the root cause.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/jaegertracing/jaeger/blob/HEAD/cmd/jaeger/internal/extension/jaegerquery/internal/mcptools/skills/error-root-cause/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/error-root-cause, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Error Root Cause Analysis

When this applies

A trace contains one or more error spans and the user wants to know the originating failure, not just the symptoms.

Procedure

  1. Use get_trace_errors to list all error spans with their status messages.
  2. Use get_trace_topology to see the full span tree and identify parent-child relationships among the error spans.
  3. Walk from each error span toward the leaves of the tree. The deepest error span with no errored children is the most likely root cause.
  4. Use get_span_details on the candidate root-cause span(s) to inspect attributes, events, and status for the actual failure reason.
  5. Report: root-cause span (service, operation, error message), the propagation chain, and a recommendation.

Gotchas

  • Timeouts at a parent may mask the real cause in a child that was cancelled — check children of timed-out spans even if they do not have error status.
  • Multiple independent root causes can exist in a single trace.