This is documentation for the next version of Grafana. For the latest stable release, go to the latest version.
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.
Add data source
To access Jaeger settings, click the Configuration (gear) icon, then click Data Sources > Jaeger.
||The data source name in panels, queries, and Explore.|
||The pre-selected data source for a new panel.|
||The URL of the Jaeger instance. For example,
||Enable basic authentication for the Jaeger data source.|
||Specify a user name for basic authentication.|
||Specify a password for basic authentication.|
Trace to logs
Note: This feature is available in Grafana 7.4+.
This is a configuration for the trace to logs feature. Select target data source (at this moment limited to Loki data sources) and select which tags will be used in the logs query.
- Data source - Target data source.
- Tags - The tags that will be used in the Loki query. Default is
'cluster', 'hostname', 'namespace', 'pod'.
You can query and display traces from Jaeger via Explore.
You can query by trace ID or use the search form to find traces. To query by trace ID, select the TraceID from the Query type selector and insert the ID into the text input.
To perform a search, set the query type selector to Search, then use the following fields to find traces:
- Service - Returns a list of services.
- Operation - Field gets populated once you select a service. It then lists the operations related to the selected service. Select
Alloption to query all operations.
- Tags - Use values in the logfmt format. For example
error=true db.statement="select * from User".
- Min Duration - Filter all traces with a duration higher than the set value. Possible values are
1.2s, 100ms, 500us.
- Max Duration - Filter all traces with a duration lower than the set value. Possible values are
1.2s, 100ms, 500us.
- Limit - Limits the number of traces returned.
Linking Trace ID from logs
Configure the data source with provisioning
You can set up the data source via configuration files with Grafana’s provisioning system. Refer to provisioning docs page for more information on configuring various settings.
Here is an example with basic auth and trace-to-logs field.
apiVersion: 1 datasources: - name: Jaeger type: jaeger uid: jaeger-spectra access: proxy url: http://localhost:16686/ basicAuth: true basicAuthUser: my_user editable: true isDefault: false jsonData: tracesToLogs: # Field with internal link pointing to a Loki data source in Grafana. # datasourceUid value must match the `datasourceUid` value of the Loki data source. datasourceUid: loki tags: - cluster - hostname - namespace - pod secureJsonData: basicAuthPassword: my_password
Related Grafana resources
GrafanaCONline 2021 is coming June 7-17
Be the first to learn about exciting next-generation features in Grafana 8.0, be inspired by what community members are building, and attend expert-led sessions and workshops on Grafana, Prometheus, Loki logs, and more.
Unify your data with Grafana plugins: Splunk, MongoDB, Datadog, and more
Show how Grafana can be used to take data from multiple different sources and unify it, without disrupting the investments that are working today.
Demo: Getting started with Grafana Enterprise and observability
Join the Grafana Labs team for a 30-minute demo of how to get started with the Grafana Stack, so you can go from zero to observability in just a few minutes.