mirror of
https://github.com/grafana/grafana.git
synced 2025-07-29 01:42:29 +08:00
90303b5a03
* moved datasources folder * Update menu.yaml * updated Azuremonitor * Update azuremonitor.md * Update cloudmonitoring.md * Update cloudwatch.md * updated content * Update elasticsearch.md * Update graphite.md * Update elasticsearch.md * Update azuremonitor.md * Update cloudmonitoring.md * Update influxdb.md * Update jaeger.md * Update loki.md * Update mssql.md * Update mysql.md * Update opentsdb.md * Update postgres.md * Update prometheus.md * Update postgres.md * Update jaeger.md * Update mysql.md * Update mssql.md * added aliases * Update testdata.md * Update zipkin.md * link fixes * link fixing * moved files out of guides * Delete archive.md * updated links * updated aliases * updated aliases * link updates * Update _index.md * deleted archive.md * Update azuremonitor.md * Update azuremonitor.md
49 lines
3.3 KiB
Markdown
49 lines
3.3 KiB
Markdown
+++
|
|
title = "Jaeger"
|
|
description = "Guide for using Jaeger in Grafana"
|
|
keywords = ["grafana", "jaeger", "guide", "tracing"]
|
|
type = "docs"
|
|
aliases = ["/docs/grafana/latest/features/datasources/jaeger"]
|
|
[menu.docs]
|
|
name = "Jaeger"
|
|
parent = "datasources"
|
|
weight = 800
|
|
+++
|
|
|
|
# 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]({{< relref "../explore/index.md" >}}).
|
|
|
|
## Adding the data source
|
|
To access Jaeger settings, click the **Configuration** (gear) icon, then click **Data Sources**, and then click **Jaeger**.
|
|
|
|
| Name | Description |
|
|
| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
| _Name_ | The data source name. This is how you refer to the data source in panels, queries, and Explore. |
|
|
| _Default_ | Default data source means that it will be pre-selected for new panels. |
|
|
| _URL_ | The URL of the Jaeger instance, e.g., `http://localhost:16686` |
|
|
| _Access_ | Server (default) = URL needs to be accessible from the Grafana backend/server, Browser = URL needs to be accessible from the browser. |
|
|
| _Basic Auth_ | Enable basic authentication to the Jaeger data source. |
|
|
| _User_ | User name for basic authentication. |
|
|
| _Password_ | Password for basic authentication. |
|
|
|
|
## Query traces
|
|
|
|
You can query and display traces from Jaeger via [Explore]({{< relref "../explore/index.md" >}}).
|
|
|
|
{{< docs-imagebox img="/img/docs/v70/jaeger-query-editor.png" class="docs-image--no-shadow" caption="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.
|
|
|
|
{{< docs-imagebox img="/img/docs/v70/jaeger-query-editor-open.png" class="docs-image--no-shadow" caption="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.
|
|
1. Particular operation is part of the selected service.
|
|
1. 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]({{< relref "loki.md#derived-fields" >}}) section in the [Loki data source]({{< relref "loki.md" >}}) documentation for details.
|