jaeger-analysis

Name: jaeger-analysis
Availability: InStock
Author: IncidentFox

Analyze Jaeger traces to identify latency issues and errors across services.

654|77|Updated Jan 20, 2026

Search Tags:#observability #tracing #latency #SRE #root-cause #distributed-tracing #jaeger

Ready to run

npx skills add https://github.com/incidentfox/incidentfox --skill jaeger-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jaeger-analysis
Source: https://github.com/incidentfox/incidentfox/tree/main/sre-agent/.claude/skills/observability-jaeger
Command: npx skills add https://github.com/incidentfox/incidentfox --skill jaeger-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jaeger-client, and includes scripts (resource) components.

What problem does it solve?

Jaeger traces are essential for understanding latency and errors in distributed systems. This skill provides a structured way to analyze traces, identify bottlenecks, and understand cross-service dependencies to improve performance and reliability.

Core Features & Use Cases

End-to-end latency analysis: identify slow spans and bottlenecks across services.
Error correlation: surface traces with errors and determine impact on user requests.
Dependency mapping: reveal how services interact and where latency accumulates.

Quick Start

Use the jaeger-analysis skill to quickly inspect traces for a given service. For example:

List services: python .claude/skills/observability-jaeger/scripts/list_services.py
Get latency stats: python .claude/skills/observability-jaeger/scripts/get_latency_stats.py --service frontend
Inspect a trace: python .claude/skills/observability-jaeger/scripts/get_trace.py <trace-id>

Frequently Asked Questions about jaeger-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify latency bottlenecks in distributed tracing data?▼

To identify latency bottlenecks in distributed tracing data, analyze Jaeger traces to locate slow spans, compute latency statistics, and map service dependencies for root-cause analysis. This reveals where latency accumulates across services.

What is the best way to correlate errors across services using Jaeger traces?▼

Correlating errors across services using Jaeger traces involves parsing distributed tracing data to surface traces with errors. This determines the impact of trace errors on user requests and pinpoints the root cause.

How do I query the Jaeger API to compute latency statistics for a specific service?▼

Query the Jaeger API to compute latency statistics for a specific service by using the jaeger-client library. Run scripts to list services, fetch latency stats, and inspect individual traces to debug end-to-end performance.

Does Jaeger analysis require the jaeger-client library to map service dependencies?▼

Yes, Jaeger analysis requires the jaeger-client library to map service dependencies. The library queries the Jaeger API, parses spans, and computes latency statistics to reveal how services interact and where latency accumulates.

Can I inspect a specific trace ID to debug end-to-end performance issues?▼

Yes, you can inspect a specific trace ID to debug end-to-end performance issues. Passing a trace ID to the analysis script parses spans and traces to locate slow segments and understand cross-service dependencies.