Distributed tracing backend and utility suite for running Jaeger, generating traces, and operating Jaeger storage.
$docker run --rm --name jaeger -p 16686:16686 -p 4317:4317 -p 4318:4318 jaegertracing/jaeger:latest
Agent Compatibility
JSON Output
Agent Skill
MCP Support
AI Analysis
Jaeger tooling is the Jaeger project's suite of binaries for running the tracing backend and handling related storage or test-traffic tasks. The main jaeger binary starts a config-driven backend, while companion tools cover trace generation and storage operations.
What It Enables
- Start an all-in-one or config-driven Jaeger backend that exposes the UI, query APIs, remote sampling, and the built-in MCP extension.
- Generate steady trace traffic with
tracegenfor pipeline testing, sampling checks, and performance tuning. - Run storage-side maintenance with
jaeger-remote-storage,jaeger-es-rollover, andjaeger-es-index-cleanerwhen operating Jaeger deployments.
Agent Fit
- The binaries are non-interactive and config-driven, so starting services, checking health, printing config, and running storage maintenance fit scripts and CI well.
- Direct CLI inspection is limited; most real trace analysis happens through the HTTP query API, UI, or MCP endpoint rather than structured terminal output.
- Built-in MCP support is useful for agent drill-down, but it is exposed over HTTP and depends on a running Jaeger query service.
Caveats
- This is a multi-binary suite rather than a single focused client CLI, so the entry is broader and less discoverable than tools with one command surface.
- The recommended quick start is container-first and YAML-config driven, which is heavier than typical terminal-first admin or query CLIs.