mirror of
https://github.com/grafana/grafana.git
synced 2025-07-31 05:32:15 +08:00
b3838d372e
* Remove feature flag * Add data source setting for Jaeger * Refactor trace to logs settings * Fix tests * Get ds settings in two steps * Add info to settings * Update docs for trace to logs * Update yarn.lock * Apply suggestions from code review Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> * Update TraceToLogsSettings after merge with master * Add config for tags * Add tags to check for keys * Apply suggestions from code review Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> * Update docs Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com>
60 lines
3.7 KiB
Markdown
60 lines
3.7 KiB
Markdown
+++
|
|
title = "Zipkin"
|
|
description = "Guide for using Zipkin in Grafana"
|
|
keywords = ["grafana", "zipkin", "guide", "tracing"]
|
|
aliases = ["/docs/grafana/latest/datasources/zipkin"]
|
|
weight = 1600
|
|
+++
|
|
|
|
# Zipkin data source
|
|
|
|
Grafana ships with built-in support for Zipkin, an open source, distributed tracing system.
|
|
Just add it as a data source and you are ready to query your traces in [Explore]({{< relref "../explore" >}}).
|
|
|
|
## Adding the data source
|
|
|
|
To access Zipkin settings, click the **Configuration** (gear) icon, then click **Data Sources** > **Zipkin**.
|
|
|
|
| Name | Description |
|
|
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
|
|
| `Name` | The data source name. This is how you refer to the data source in panels, queries, and Explore. |
|
|
| `Default` | Data source will be pre-selected for new panels. |
|
|
| `URL` | The URL of the Zipkin instance, e.g., `http://localhost:9411`. |
|
|
| `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 Zipkin data source. |
|
|
| `User` | User name for basic authentication. |
|
|
| `Password` | Password for basic authentication. |
|
|
|
|
### Trace to logs
|
|
|
|
{{< docs-imagebox img="/img/docs/v74/trace-to-logs-settings.png" class="docs-image--no-shadow" caption="Screenshot of the trace to logs settings" >}}
|
|
|
|
This is a configuration for the [trace to logs feature]({{< relref "../explore/index.md#trace-to-logs" >}}). 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'`.
|
|
|
|
## Query traces
|
|
|
|
Querying and displaying traces from Zipkin is available via [Explore]({{< relref "../explore" >}}).
|
|
|
|
{{< docs-imagebox img="/img/docs/v70/zipkin-query-editor.png" class="docs-image--no-shadow" caption="Screenshot of the Zipkin query editor" >}}
|
|
|
|
The Zipkin 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/zipkin-query-editor-open.png" class="docs-image--no-shadow" caption="Screenshot of the Zipkin 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.
|
|
|
|
## Data mapping in the trace UI
|
|
|
|
Zipkin annotations are shown in the trace view as logs with annotation value shown under annotation key.
|
|
|
|
## Linking Trace ID from logs
|
|
|
|
You can link to Zipkin trace from logs in Loki by configuring a derived field with internal link. See [Loki documentation]({{< relref "loki#derived-fields" >}}) for details.
|