Zipkin data source on Grafana Labs

Configure the Zipkin data source

Thu, 11 Jun 2026 09:38:11 +0000

Configure the Zipkin data source

This document explains how to configure the Zipkin data source in Grafana, including connection settings, authentication, trace-to-logs and trace-to-metrics integrations, and provisioning with YAML or Terraform.

Before you begin

Before configuring the data source, ensure you have:

Grafana permissions: Organization administrator role
Zipkin instance: A running Zipkin instance accessible from your Grafana server

Add the data source

To add the Zipkin data source:

Click Connections in the left-side menu.
Click Add new connection.
Type Zipkin in the search bar.
Select Zipkin.
Click Add new data source.

Configure settings

The following table describes the basic configuration settings for the Zipkin data source.

Setting	Description
Name	The name used to refer to the data source in panels and queries.
Default	Toggle to make this the default data source for new panels.
URL	The URL of the Zipkin instance, such as `http://localhost:9411`.

Authentication

The Zipkin data source supports the following authentication methods:

Basic authentication: Provide a username and password to authenticate with the Zipkin instance.
TLS client authentication: Configure client certificates for mutual TLS.
Forward OAuth identity: Forward the user’s OAuth token to the Zipkin instance.
With credentials: Send credentials (cookies, TLS client certificates) with cross-site requests.

You can also configure custom headers and TLS settings in the Advanced HTTP settings section, which is located inside Additional settings.

Trace to logs

Note
If you use Grafana Cloud, open a support ticket in the Cloud Portal to access this feature.

The Trace to logs setting configures the trace to logs feature that is available when you integrate Grafana with Zipkin. This feature lets you navigate from a span in a trace view directly to the relevant logs.

There are two ways to configure the trace to logs feature:

Use a simplified configuration with a default query, or
Configure a custom query where you can use a template language to interpolate variables from the trace or span.

Use a simple configuration

Select the target data source from the drop-down list.

You can also click Open advanced data source picker to see more options, including adding a data source.
Set start and end time shift. Since the log timestamps may not exactly match the timestamps of the spans in the trace, you may need to widen or shift the time range to find the desired logs.
Select which tags to use in the logs query. The tags you configure must be present in the span attributes or resources for a trace to logs span link to appear. You can optionally configure a new name for the tag. This is useful if the tag has dots in the name and the target data source doesn’t allow dots in labels. For example, you can remap http.status to http_status.
Optionally, switch on the Filter by trace ID and/or Filter by span ID setting to further filter the logs if your logs consistently contain trace or span IDs.

Configure a custom query

Select the target data source from the drop-down list.

You can also click Open advanced data source picker to see more options, including adding a data source.
Set start and end time shift. Since the log timestamps may not exactly match the timestamps of the spans in the trace, you may need to widen or shift the time range to find the desired logs.
Optionally, select tags to map. These tags can be used in the custom query with the ${__tags} variable. This variable interpolates the mapped tags as a list in an appropriate syntax for the data source and only includes tags that are present in the span. You can optionally configure a new name for the tag. This is useful when the tag has dots in the name and the target data source doesn’t allow dots in labels. For example, you can remap http.status to http_status. If you don’t map any tags here, you can still use any tag in the query like this: method="${__span.tags.method}".
Skip Filter by trace ID and Filter by span ID settings as these can’t be used with a custom query.
Switch on Use custom query.
Specify a custom query to be used to query the logs. You can use various variables to make the query relevant for the current span. The link only appears if all the variables are interpolated with non-empty values to prevent creating an invalid query.

Variables for custom queries

To use a variable, wrap it in ${}. For example: ${__span.name}.

Variable name	Description
__tags	This variable uses the tag mapping from the UI to create a label matcher string in the specific data source syntax. The variable only uses tags that are present in the span. The link is still created even if only one of those tags is present in the span. You can use this if all tags aren’t required for the query to be useful.
__span.spanId	The ID of the span.
__span.traceId	The ID of the trace.
__span.duration	The duration of the span.
__span.name	The name of the span.
__span.tags	Namespace for the tags in the span. To access a specific tag named `version`, you would use `${__span.tags.version}`. If the tag contains a dot, access it as `${__span.tags["http.status"]}`.
__trace.traceId	The ID of the trace.
__trace.duration	The duration of the trace.
__trace.name	The name of the trace.

Trace to logs settings

The following table describes the trace to logs configuration options.

Setting name	Description
Data source	Defines the target data source. You can select Loki, Elasticsearch, Splunk, OpenSearch, FalconLogScale, Google Cloud Logging, and VictoriaMetrics Logs data sources.
Span start time shift	Shifts the start time for the logs query, based on the span’s start time. You can use time units, such as `5s`, `1m`, `3h`. To extend the time to the past, use a negative value. Default: `0`.
Span end time shift	Shifts the end time for the logs query, based on the span’s end time. You can use time units. Default: `0`.
Tags	Defines the tags to use in the logs query. Default: `cluster`, `hostname`, `namespace`, `pod`, `service.name`, `service.namespace`. You can change the tag name to remove dots from the name if they aren’t allowed in the target data source. For example, map `http.status` to `http_status`.
Filter by trace ID	Toggles whether to append the trace ID to the logs query.
Filter by span ID	Toggles whether to append the span ID to the logs query.
Use custom query	Toggles use of custom query with interpolation.
Query	Input to write a custom query. Use variable interpolation to customize it with variables from the span.

Trace to metrics

The Trace to metrics setting lets you navigate from a span in a trace view to a metrics query in a configured metrics data source.

To configure trace to metrics:

Select the target data source from the drop-down list.

You can also click Open advanced data source picker to see more options, including adding a data source.
Create any desired linked queries.

Setting name	Description
Data source	Defines the target data source.
Tags	Defines the tags used in linked queries. The key sets the span attribute name, and the optional value sets the corresponding metric label name. For example, you can map `k8s.pod` to `pod`. To interpolate these tags into queries, use the `$__tags` keyword.

Each linked query consists of:

Link Label: (Optional) Descriptive label for the linked query.
Query: The query run when navigating from a trace to the metrics data source. Interpolate tags using the $__tags keyword. For example, when you configure the query requests_total{$__tags} with the tags k8s.pod=pod and cluster, the result looks like requests_total{pod="nginx-554b9", cluster="us-east-1"}.

Additional settings

The Additional settings section is collapsible and contains optional settings for the node graph, span bar, advanced HTTP configuration, and secure SOCKS proxy (when enabled in your Grafana configuration).

Node graph

The Enable node graph toggle enables the Node graph visualization, which is disabled by default.

After you enable it, Grafana displays the node graph above the trace view.

Span bar

The Span bar setting lets you display additional information in the span bar row.

The Label drop-down has three options:

Label	Description
None	Adds nothing to the span bar row.
Duration	(Default) Displays the span duration on the span bar row.
Tag	Displays the span tag on the span bar row. Enter the Tag key to specify which tag value to display, such as `component`.

Verify the connection

Click Save & test to verify the connection. A successful connection displays the message Data source is working.

If you encounter errors, refer to Troubleshoot Zipkin data source issues.

Provision the data source

You can define and configure the data source in YAML files as part of the Grafana provisioning system. For more information about provisioning and available configuration options, refer to Provisioning Grafana.

Provisioning example

apiVersion: 1

datasources:
  - name: Zipkin
    type: zipkin
    uid: zipkin-ds
    url: http://localhost:9411
    access: proxy
    basicAuth: true
    basicAuthUser: my_user
    readOnly: false
    isDefault: false
    jsonData:
      tracesToLogsV2:
        datasourceUid: 'loki'
        spanStartTimeShift: '1h'
        spanEndTimeShift: '-1h'
        tags: ['job', 'instance', 'pod', 'namespace']
        filterByTraceID: false
        filterBySpanID: false
        customQuery: true
        query: 'method="$${__span.tags.method}"'
      tracesToMetrics:
        datasourceUid: 'prom'
        spanStartTimeShift: '1h'
        spanEndTimeShift: '-1h'
        tags: [{ key: 'service.name', value: 'service' }, { key: 'job' }]
        queries:
          - name: 'Sample query'
            query: 'sum(rate(traces_spanmetrics_latency_bucket{$$__tags}[5m]))'
      nodeGraph:
        enabled: true
      spanBar:
        type: 'None'
    secureJsonData:
      basicAuthPassword: my_password

Configure with Terraform

You can configure the Zipkin data source using Terraform with the Grafana Terraform provider.

For more information about provisioning resources with Terraform, refer to the Grafana as code using Terraform documentation.

Basic Terraform example

The following example creates a basic Zipkin data source:

resource "grafana_data_source" "zipkin" {
  name = "Zipkin"
  type = "zipkin"
  url  = "http://localhost:9411"
}

Terraform example with trace to logs

The following example includes a trace to logs configuration that links traces to a Loki data source:

resource "grafana_data_source" "zipkin" {
  name = "Zipkin"
  type = "zipkin"
  url  = "http://localhost:9411"

  json_data_encoded = jsonencode({
    tracesToLogsV2 = {
      datasourceUid    = grafana_data_source.loki.uid
      spanStartTimeShift = "1h"
      spanEndTimeShift   = "-1h"
      filterByTraceID  = true
      filterBySpanID   = false
      tags = [
        { key = "service.name", value = "service" },
        { key = "namespace" }
      ]
    }
    nodeGraph = {
      enabled = true
    }
  })
}

Terraform example with basic authentication

The following example includes basic authentication:

resource "grafana_data_source" "zipkin" {
  name = "Zipkin"
  type = "zipkin"
  url  = "http://localhost:9411"

  basic_auth_enabled  = true
  basic_auth_username = "zipkin_user"

  secure_json_data_encoded = jsonencode({
    basicAuthPassword = var.zipkin_password
  })

  json_data_encoded = jsonencode({
    nodeGraph = {
      enabled = true
    }
  })
}

For all available configuration options, refer to the Grafana provider data source resource documentation.

Zipkin query editor

Thu, 11 Jun 2026 09:38:11 +0000

Zipkin query editor

This document explains how to use the Zipkin query editor to query and visualize traces. You can look up traces by ID, browse available traces using the cascading service and span selector, or upload a JSON trace file for visualization.

For general documentation on querying data sources in Grafana, refer to Query and transform data.

Query by trace ID

To query a specific trace by its ID:

Select the TraceID query type.
Enter the trace ID into the Trace ID field.
Press Shift+Enter to run the query.

Zipkin trace IDs are 16 or 32 character hexadecimal strings, for example efe9cb8857f68c8f or 463ac35c9f6413ad48485a3953bb6124.

You can also use template variables in the trace ID field. For example, ${traceId} is replaced with the variable’s current value when the query runs.

Query by trace selector

You can browse and select traces using the Traces cascading selector instead of entering a trace ID manually. This is useful when you want to explore traces without knowing a specific trace ID.

The trace selector has three levels:

Service: Select the service you’re interested in, such as frontend or api-gateway.
Span: Select a specific operation within the selected service, such as GET /api/users.
Trace: Select a specific trace in which the selected operation occurred, represented by the root operation name and trace duration (for example, get /api [23 ms]).

When you select a trace at the third level, the trace ID is automatically populated and the query runs.

Note
The trace selector lists traces within the currently selected Explore time range. If you don’t see expected traces, try expanding the time range.

Upload a JSON trace file

You can upload a JSON file that contains a single trace and visualize it. If the file has multiple traces, Grafana visualizes the first trace.

To upload a trace file:

Click Import trace.
Drag and drop a JSON file or click to browse for a file.

The file must contain a JSON array of spans in the Zipkin v2 span format.

Single-span trace example

[
  {
    "traceId": "efe9cb8857f68c8f",
    "id": "efe9cb8857f68c8f",
    "kind": "SERVER",
    "name": "get /api",
    "timestamp": 1627975249601797,
    "duration": 23457,
    "localEndpoint": { "serviceName": "backend", "ipv4": "127.0.0.1", "port": 9000 },
    "tags": {
      "http.method": "GET",
      "http.path": "/api"
    }
  }
]

Multi-span trace example

The following example shows a trace with a parent span and a child span, representing a frontend service calling a backend service:

[
  {
    "traceId": "efe9cb8857f68c8f",
    "id": "efe9cb8857f68c8f",
    "kind": "SERVER",
    "name": "get /api",
    "timestamp": 1627975249601797,
    "duration": 23457,
    "localEndpoint": { "serviceName": "frontend", "ipv4": "127.0.0.1", "port": 8080 },
    "tags": {
      "http.method": "GET",
      "http.path": "/api",
      "http.status_code": "200"
    }
  },
  {
    "traceId": "efe9cb8857f68c8f",
    "parentId": "efe9cb8857f68c8f",
    "id": "8608dc6ce5cafe8e",
    "kind": "CLIENT",
    "name": "get /api/data",
    "timestamp": 1627975249602000,
    "duration": 18200,
    "localEndpoint": { "serviceName": "backend", "ipv4": "127.0.0.1", "port": 9000 },
    "tags": {
      "http.method": "GET",
      "http.path": "/api/data",
      "http.status_code": "200"
    }
  }
]

View data mapping in the trace UI

Zipkin annotations appear in the trace view as logs with the annotation value displayed under the annotation key. This lets you view timestamped events that occurred during a span, such as retry attempts or cache misses.

Span filters

Using span filters, you can filter spans in the trace timeline viewer. The more filters you add, the more specific the filtered spans are.

You can add one or more of the following filters:

Filter	Description	Example
Service name	Filter by the service that produced the span.	`frontend`
Span name	Filter by the operation name.	`GET /api/users`
Duration	Filter by minimum and/or maximum span duration.	Min: `10ms`, Max: `500ms`
Tags	Filter by span tags, process tags, or log fields.	`http.status_code=500`

To only show the spans you have matched, toggle on Show matches only.

Span filter examples

Find slow database calls: Set Service name to your database service and Duration minimum to 100ms.
Find errors: Add a Tags filter for error=true or http.status_code=500.
Isolate a specific service: Set Service name and toggle on Show matches only to hide all other spans.

Link to a trace ID from logs

You can link to Zipkin traces from logs in Loki, Elasticsearch, Splunk, and other logs data sources by configuring an internal link.

To configure this feature, refer to the Derived fields section of the Loki data source docs or the Data links section of the Elasticsearch or Splunk data source docs.

Link to a trace ID from metrics

You can link to Zipkin traces from metrics in Prometheus data sources by configuring an exemplar.

To configure this feature, refer to the introduction to exemplars documentation.

Troubleshoot query issues

If you encounter issues with queries, refer to Troubleshoot Zipkin data source issues.

Zipkin template variables

Thu, 11 Jun 2026 09:38:11 +0000

Zipkin template variables

Use template variables to create dynamic, reusable dashboards. Instead of hard-coding trace IDs, you can use variables to let dashboard viewers select or input trace IDs at view time, making it easier to share dashboards across teams.

For an introduction to Grafana template variables, refer to Variables.

Supported variable types

Variable type	Description	Supported
Custom	Define a fixed list of trace IDs or other values.	Yes
Text box	Let users type a trace ID at dashboard view time.	Yes
Data source	Let users switch between Zipkin instances.	Yes
Query	Populate options from a data source query.	No

The Zipkin data source doesn’t support query-based variables, but you can use custom or text box variables to parameterize trace ID queries.

Create a text box variable

A text box variable lets dashboard viewers enter a trace ID directly. This is the most common variable type for Zipkin.

To create a text box variable:

Navigate to Dashboard settings > Variables.
Click Add variable.
Select Textbox as the variable type.
Set the Name to traceId.
Optionally, set a Default value with a known trace ID for initial display.
Click Apply.

The dashboard displays a text input where viewers can paste a trace ID.

Create a custom variable

A custom variable provides a predefined list of values. This is useful when you want to give viewers a set of known trace IDs to choose from.

To create a custom variable:

Navigate to Dashboard settings > Variables.
Click Add variable.
Select Custom as the variable type.
Set the Name to traceId.
Enter trace IDs in the Values separated by comma field:
```
efe9cb8857f68c8f,463ac35c9f6413ad48485a3953bb6124
```
Click Apply.

The dashboard displays a drop-down where viewers can select from the predefined trace IDs.

Create a data source variable

A data source variable lets viewers switch between multiple Zipkin instances. This is useful when you have separate Zipkin deployments for different environments.

To create a data source variable:

Navigate to Dashboard settings > Variables.
Click Add variable.
Select Data source as the variable type.
Set the Name to zipkinDs.
Select Zipkin as the Type.
Click Apply.

Then, in your panel’s query editor, select ${zipkinDs} as the data source instead of a specific Zipkin instance.

Use variables in queries

You can use template variables in the Trace ID field of the query editor. Grafana replaces the variable with its current value when the query runs.

For example, if you create a text box variable named traceId, enter ${traceId} in the trace ID field. When the viewer enters a new trace ID, the query automatically runs with the new value.

For more information about variable syntax, refer to Variable syntax.

Troubleshoot template variable issues

If template variables aren’t working as expected, refer to Troubleshoot Zipkin data source issues.

Troubleshoot Zipkin data source issues

Thu, 11 Jun 2026 09:38:11 +0000

Troubleshoot Zipkin data source issues

This document provides solutions to common issues you may encounter when configuring or using the Zipkin data source, including connection failures, query errors, JSON upload issues, and configuration problems. For configuration instructions, refer to Configure Zipkin.

Connection errors

These errors occur when Grafana can’t connect to the Zipkin instance.

`error reading settings: url is empty`

Symptoms:

Save & test fails immediately
Health check returns an error

Solutions:

Open the data source settings and verify the URL field isn’t empty.
Enter the full URL of your Zipkin instance, such as http://localhost:9411.

“request failed: 404 Not Found” or other HTTP status errors

Symptoms:

Save & test fails with an HTTP status error
Trace queries return errors

Possible causes and solutions:

Cause	Solution
Incorrect URL or port	Verify the URL and port. The default Zipkin port is `9411`. Ensure you haven’t accidentally used the Jaeger port (`16686`).
Missing `/api/v2` path	The Zipkin data source calls `/api/v2/services`, `/api/v2/traces`, etc. Verify these endpoints are accessible at the configured URL.
Reverse proxy misconfiguration	If using a reverse proxy, ensure it correctly forwards requests to the Zipkin API.
Authentication failure	If the Zipkin instance requires authentication, verify your credentials are correct.

`error creating http client` or TLS errors

Symptoms:

Save & test fails with a connection or TLS error
HTTPS connections are refused

Solutions:

If using HTTPS, verify the TLS certificate is valid and trusted by the Grafana server.
Configure TLS settings in Additional settings > Advanced HTTP settings.
For self-signed certificates, add the CA certificate to the Grafana server trust store or toggle Skip TLS Verify (not recommended for production).

Save & test times out

Symptoms:

Save & test hangs and eventually times out
No error message is returned

Possible causes and solutions:

Cause	Solution
Zipkin instance is down	Confirm the Zipkin instance is running and accessible from the Grafana server.
Firewall or network rules	Ensure the Grafana server can reach the Zipkin instance. Check that firewall rules allow outbound traffic on the configured port.
DNS resolution failure	Verify the hostname in the URL resolves correctly from the Grafana server.

For Grafana Cloud, if you’re accessing a private Zipkin instance, configure Private data source connect.

Query editor errors

These errors occur when using the query editor in Explore or dashboards.

“Failed to load spans from Zipkin”

Symptoms:

Error message appears in the query editor
The Traces cascading selector doesn’t populate services, spans, or traces

This error occurs when the frontend can’t reach the Zipkin API endpoints (/api/v2/services, /api/v2/spans, or /api/v2/traces).

Solutions:

Verify the Zipkin instance is running and accessible.
Test the endpoint directly: curl http://<ZIPKIN_URL>/api/v2/services.
Check that the Grafana server can reach the Zipkin API.
Review the Grafana server logs for more details. Look for An error occurred while doing a resource call in the logs.

“An error occurred within the plugin”

Symptoms:

A generic error appears when querying or browsing traces
No specific error details are shown in the UI

This is a generic error returned by the Zipkin plugin backend when an internal error occurs. The actual error details are only available in the Grafana server logs.

Solutions:

Enable debug logging to capture detailed error information.
Check the Grafana server logs for messages like An error occurred while doing a resource call or An error occurred while processing response from resource call.
Verify the Zipkin instance is healthy and responding to API requests.

“No data” or empty results

Symptoms:

Query runs without error but returns no data
Trace view shows “No data”
The cascading selector shows “No traces found” or “[No traces in time range]”

Possible causes and solutions:

Cause	Solution
Invalid trace ID	Verify the trace ID is correct. Zipkin trace IDs are 16 or 32 character hex strings.
Empty trace ID	Ensure the Trace ID field isn’t empty. The backend rejects queries with `invalid/empty traceId`.
Time range doesn’t contain data	Expand the dashboard or Explore time range. Traces must fall within the selected time range for the cascading selector to find them.
Trace has expired	Zipkin may have purged old trace data based on its retention settings. Check your Zipkin storage configuration.
No services registered	If the cascading selector shows “No traces found” at the top level, your Zipkin instance may have no data. Verify data is being collected.

Upload errors

These errors occur when importing a JSON trace file.

“JSON is not valid Zipkin format”

Symptoms:

Error appears after uploading a JSON trace file
The trace doesn’t render

Possible causes and solutions:

Cause	Solution
Invalid JSON syntax	Validate the file with a JSON linter. Common issues include trailing commas, missing quotes, or unclosed brackets.
Wrong JSON structure	The file must be a JSON array of span objects (`[{...}, {...}]`), not a single object. Refer to the Zipkin v2 span format.
Wrong file type	Ensure you’re uploading a `.json` file, not a different format.

`unsupported query type upload. only available in frontend mode`

Symptoms:

Error when trying to use uploaded trace data in a dashboard panel or alert

Upload queries only work in Explore. They can’t be used in dashboard panels or alerting rules because the upload is processed in the browser, not the backend.

Solution:

Use the TraceID query type with the trace ID from your uploaded trace if you need to display it in a dashboard. This requires the trace to exist in your Zipkin instance.

Configuration errors

These errors relate to data source configuration settings.

Symptoms:

Error appears in the trace to logs or trace to metrics configuration
The Span start time shift or Span end time shift field is highlighted

Solutions:

Use valid time unit formats: 5s, 1m, 3h, -30m.
Use a negative value to shift the time to the past (for example, -1h).
The value must be a number followed by a time unit (s, m, h).

Trace to logs links don’t appear

Symptoms:

No log links appear in the trace view
Links appear for some spans but not others

Possible causes and solutions:

Cause	Solution
Tags not present in span	The tags configured in trace to logs settings must exist in the span attributes for the link to appear. Verify the span contains the expected tags.
Logs data source not configured	Ensure the target logs data source (Loki, Elasticsearch, Splunk, OpenSearch, FalconLogScale, Google Cloud Logging, or VictoriaMetrics Logs) is configured and working.
Custom query variables not resolved	If using a custom query, the link only appears when all variables resolve to non-empty values. Verify the span contains the referenced tags.
Wrong data source type selected	The trace to logs data source must be a supported logs data source. Other data source types don’t appear in the drop-down.

Trace to metrics links don’t appear

Symptoms:

No metrics links appear in the trace view

Solutions:

Verify the target metrics data source is configured and working.
Ensure linked queries are defined with valid query syntax.
Check that the $__tags keyword in queries maps to tags that exist in the span.

Template variable errors

These errors relate to using template variables with the Zipkin data source.

Variable value not substituted in query

Symptoms:

The trace ID field shows the variable syntax (for example, ${traceId}) instead of the actual value
Query returns no results when using a variable

Solutions:

Verify the variable is defined in Dashboard settings > Variables.
Check the variable name matches the syntax used in the query. Variable names are case-sensitive.
Ensure the variable has a value selected or entered.
For text box variables, verify the viewer has entered a value.

Enable debug logging

To capture detailed error information for troubleshooting:

Set the Grafana log level to debug in the configuration file:
ini
```
[log]
level = debug
```
Review logs in /var/log/grafana/grafana.log (or your configured log location).
Look for Zipkin-specific entries that include request and response details, such as:
- Failed to close response body
- An error occurred while doing a resource call
- An error occurred while processing response from resource call
Reset the log level to info after troubleshooting to avoid excessive log volume.

Get additional help

If you’ve tried these solutions and still encounter issues:

Check the Grafana community forums for similar issues.
Review the Grafana GitHub issues for known bugs.
Consult the Zipkin documentation for service-specific guidance.
Contact Grafana Support if you have a paid plan. Open a support ticket for Grafana Cloud, or contact support for Grafana Enterprise.
When reporting issues, include:
- Grafana version
- Error messages (redact sensitive information)
- Steps to reproduce
- Relevant configuration (redact credentials)

Zipkin data source on Grafana Labs

Configure the Zipkin data source

Configure the Zipkin data source

Before you begin

Add the data source

Configure settings

Authentication

Trace to logs

Use a simple configuration

Configure a custom query

Variables for custom queries

Trace to logs settings

Trace to metrics

Additional settings

Node graph

Span bar

Verify the connection

Provision the data source

Provisioning example

Configure with Terraform

Basic Terraform example

Terraform example with trace to logs

Terraform example with basic authentication

Zipkin query editor

Zipkin query editor

Query by trace ID

Query by trace selector

Upload a JSON trace file

Single-span trace example

Multi-span trace example

View data mapping in the trace UI

Span filters

Span filter examples

Link to a trace ID from logs

Link to a trace ID from metrics

Troubleshoot query issues

Zipkin template variables

Zipkin template variables

Supported variable types

Create a text box variable

Create a custom variable

Create a data source variable

Use variables in queries

Troubleshoot template variable issues

Troubleshoot Zipkin data source issues

Troubleshoot Zipkin data source issues

Connection errors

error reading settings: url is empty

“request failed: 404 Not Found” or other HTTP status errors

error creating http client or TLS errors

Save & test times out

Query editor errors

“Failed to load spans from Zipkin”

“An error occurred within the plugin”

“No data” or empty results

Upload errors

“JSON is not valid Zipkin format”

unsupported query type upload. only available in frontend mode

Configuration errors

“Invalid time shift. See tooltip for examples.”

Trace to logs links don’t appear

Trace to metrics links don’t appear

Template variable errors

Variable value not substituted in query

Enable debug logging

Get additional help

`error reading settings: url is empty`

`error creating http client` or TLS errors

`unsupported query type upload. only available in frontend mode`