Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Enterprise Open source

Jaeger data source

Grafana ships with built-in support for Jaeger, which provides open source, end-to-end distributed tracing. Just add it as a data source and you are ready to query your traces in Explore.

Adding the data source

To access Jaeger settings, click the Configuration (gear) icon, then click Data Sources, and then click Jaeger.

NameThe data source name. This is how you refer to the data source in panels, queries, and Explore.
DefaultDefault data source means that it will be pre-selected for new panels.
URLThe URL of the Jaeger instance, e.g., http://localhost:16686
AccessServer (default) = URL needs to be accessible from the Grafana backend/server, Browser = URL needs to be accessible from the browser.
Basic AuthEnable basic authentication to the Jaeger data source.
UserUser name for basic authentication.
PasswordPassword for basic authentication.

Query traces

You can query and display traces from Jaeger via Explore.

Screenshot of the Jaeger query editor
Screenshot of the Jaeger query editor

The Jaeger query editor allows you to query by trace ID directly or selecting a trace from trace selector. To query by trace ID, insert the ID into the text input.

Screenshot of the Jaeger query editor with trace selector expanded
Screenshot of the Jaeger query editor with trace selector expanded

Use the trace selector to pick particular trace from all traces logged in the time range you have selected in Explore. The trace selector has three levels of nesting:

  1. The service you are interested in.
  2. Particular operation is part of the selected service
  3. Specific trace in which the selected operation occurred, represented by the root operation name and trace duration.

Linking Trace ID from logs

You can link to Jaeger trace from logs in Loki by configuring a derived field with internal link. See the Derived fields section in the Loki data source documentation for details.