Search results
Jul 25, 2024 · Jaeger connects the dots between these disparate components, helping to identify performance bottlenecks, troubleshoot errors, and improve overall application reliability. Jaeger is 100% open source, cloud native, and infinitely scalable.
It includes the Jaeger UI, jaeger-collector, jaeger-query, and jaeger-agent, with an in memory storage component. The simplest way to start the all-in-one is to use the pre-built image published to DockerHub (a single command line).
All in One. All-in-one is an executable designed for quick local testing, launches the Jaeger UI, collector, query, and agent, with an in memory storage component. The simplest way to start the all-in-one is to use the pre-built image published to DockerHub (a single command line). $ docker run -d --name jaeger \.
jaeger-agent (deprecated) Receives spans from Jaeger clients and forwards to collector. Designed to run as a sidecar or a host agent. jaeger-agent is deprecated and no longer recommended for use, see https://github.com/jaegertracing/jaeger/issues/4739
Your applications must be instrumented before they can send tracing data to Jaeger backend. Check the Client Libraries section for information about how to use the OpenTracing API and how to initialize and configure Jaeger tracers.
Welcome to Jaeger’s documentation portal! Below, you’ll find information for beginners and experienced Jaeger users. If you cannot find what you are looking for, or have an issue not covered here, we’d love to hear from you .
Welcome to Jaeger’s documentation portal! Below, you’ll find information for beginners and experienced Jaeger users. If you can’t find what you are looking for, or have an issue not covered here, we’d love to hear from you .
command line arguments, environment variables, configuration files in JSON, TOML, YAML, HCL, or Java properties formats. To see the complete list of options, run the binary with the help command or refer to the CLI Flags page for more information.
Jaeger can be deployed either as an all-in-one binary, where all Jaeger backend components run in a single process, or as a scalable distributed system. There are two main deployment options discussed below.
APIs. Version 1.62 Latest Go to the latest 2.x version. Jaeger components implement various APIs for saving or retrieving trace data. The following labels are used to describe API compatibility guarantees. stable - the API guarantees backwards compatibility.