Jaeger
Jaeger v2 is an open-source, end-to-end distributed tracing platform based on the OpenTelemetry Collector.
Platform availability
Available on 3 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
76/100 Good
- Maintained
- 100last commit 7 days ago
- Popular
- 8723,409 GitHub stars
- Easy to install
- 452 install platforms, install notes, Docker image
- Light to run
- 208 GB minimum RAM, runs on ARM
- Security check
- 90no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 8.4/10
Availability: platform listings confirmed today, links checked 3 days ago
- GitHub stars
- 23,409
- Open issues
- 630
- Last commit
- 2026-11-14
- Latest release
- v2.23.0
- License
- Apache-2.0
- Activity
- steady
Checked 7 days ago - source: GitHub (jaegertracing/jaeger)
Resources & Compatibility
Minimum requirements: 8 GB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Start Docker with UI and trace ports mapped Run Jaeger in Docker and map 16686 for the web UI, 4317/4318 for OpenTelemetry (OTLP) trace intake, 9411 for Zipkin-compatible intake, and 5778 for older Jaeger agents, while mounting your local config.yaml into the container. Without these mappings, your browser or applications may not be able to reach the UI or send traces. source
- Tell Jaeger where to store traces In the jaeger_query section (the part that serves the UI and search), set the storage backends for traces and metrics, and make sure the API endpoint addresses match where you plan to connect from. If storage is not selected or endpoints are wrong, the UI may start but still fail to show or accept data. source
- Install Jaeger as a Windows service On Windows, use NSSM (a helper that turns a program into a service) to register Jaeger, point it at config.yaml, set files for normal and error output, and start the service. This keeps Jaeger running after the terminal is closed and gives you log files to check if something goes wrong. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives (3)
- AppDynamics - The AppDynamics platform gives today’s software-defined businesses the ability to analyze and optimize digital business performance in real…
- Netdata - Netdata is a real-time performance and health monitoring solution that collects per-second metrics from your servers, containers, networks,…
- New Relic - Pinpoint and solve performance issues in your Ruby, Java, .NET, PHP and Python apps with real user, application and server monitoring.
Checked 54 days ago - source: AlternativeTo
Common questions
Which ports should I map when running Jaeger all-in-one in Docker?
Map 16686 for the web UI and 4317/4318 for OpenTelemetry OTLP trace intake. You can also map 9411 for Zipkin-compatible intake and 5778 for older Jaeger agents. Missing mappings can prevent the UI or applications from reaching Jaeger.
Where in the Jaeger v2 configuration do I set the trace storage backend?
Set the trace and metric storage backends in the jaeger_query section of the configuration. The API endpoint addresses must match where you plan to connect, or the UI may start but fail to show or accept data.
Why can an application in a separate Docker container fail to send traces to Jaeger?
The application may not see Jaeger's host name from its network namespace. Put the containers in the same namespace or give the application container access to Jaeger's backend address.
How do I keep Jaeger running as a Windows service?
Use NSSM to register Jaeger, point it at config.yaml, set files for normal and error output, and start the service. This keeps Jaeger running after the terminal is closed and gives you log files to inspect.
Answers sourced from www.jaegertracing.io, www.jaegertracing.io, www.jaegertracing.io, www.jaegertracing.io
Community
- One backend for all? : r/OpenTelemetry - Reddit (reddit)
- Monitoring tools - recommendation (moving away from NewRelic) - Reddit (reddit)
- I really like Jaegers tracing/logging, but is it overkill to ... - Reddit (reddit)
- Jaeger alternatives? : r/devops - Reddit (reddit)
Collected 48 days ago - public community threads