Getting Started | Jaeger

If you are new to distributed tracing, please check the Introduction page.
The easiest way to run Jaeger is by starting it in a container:
This runs the all-in-one configuration of Jaeger (see Architecture) that combines collector and query components in a single process and uses a transient in-memory storage for trace data. You can navigate to http://localhost:16686 to access the Jaeger UI. See the APIs page for a full list of exposed ports.
In order to run Jaeger in other roles (see Architecture), an explicit configuration file (see Configuration) must be provided via the --config command line argument. When running in a container, the path to the config file must be mapped into the container file system (the -v ... mapping below):
HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates the use of OpenTelemetry and distributed tracing. A tutorial / walkthrough is available in the blog post: Take Jaeger for a HotROD ride.
Using this application you can:
We recommend running Jaeger and HotROD together via docker compose:
Then navigate to http://localhost:8080. See the README for other ways to run the demo.
The Service Performance Monitoring (SPM) page has its own Quick Start that shows how to explore that aspect of Jaeger.