---
title: "Configure trace to profiles correlation | Grafana documentation"
description: "Configure trace to profiles to link from Tempo spans to profiling data in Grafana Pyroscope with embedded flame graphs"
---

# Configure trace to profiles correlation

Trace to profiles lets you navigate from a span in a trace directly to profiling data in [Grafana Pyroscope](/docs/pyroscope/latest/). When configured, a **Profiles for this span** button and an embedded flame graph appear in the span details view.

## Before you begin

To configure trace to profiles, you need:

- A [Tempo data source](/docs/grafana/latest/datasources/tempo/configure-tempo-data-source/) configured in Grafana
- A [Grafana Pyroscope data source](/docs/grafana/latest/datasources/grafana-pyroscope/) configured in Grafana
- An application instrumented with the [OpenTelemetry span profiling bridge](/docs/pyroscope/latest/configure-client/trace-span-profiles/) so that spans include the `pyroscope.profile.id` attribute
- Editor or Admin permissions in Grafana

> Note
> 
> You can’t modify a provisioned data source from the Grafana UI. If you’re using Grafana Cloud Traces (the pre-configured tracing data source in Grafana Cloud), its settings are read-only. To configure trace to profiles, [clone the data source](/docs/grafana/latest/datasources/tempo/configure-tempo-data-source/provision/#clone-a-provisioned-data-source-for-grafana-cloud) to create an editable copy, or update the provisioning file for self-managed instances. Refer to the [Provisioning](#provisioning) section for details.

Using Trace to profiles, you can use the ability to correlate different signals in Grafana by adding the functionality to link between traces and profiles.

**Trace to profiles** lets you link your Grafana Pyroscope data source to tracing data. When configured, this connection lets you run queries from a trace span into the profile data using **Explore**. Each span links to your queries. Clicking a link runs the query in a split panel. If tags are configured, Grafana dynamically inserts the span attribute values into the query. The query runs over the time range of the (span start time - 60) to (span end time + 60 seconds).

Embedded flame graphs are also inserted into each span details section that has a linked profile. This lets you see resource consumption in a flame graph visualization for each span without having to navigate away from the current view.

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

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

### Before you begin

To use Trace to profiles, you need:

- A [Grafana Pyroscope data source](/docs/grafana/latest/datasources/grafana-pyroscope/) connected to your Pyroscope instance.
- A Tempo data source configured with the Trace to profiles settings described on this page.
- Your application instrumented with all three of the following:
  
  1. **Profiling**: A Pyroscope SDK or Grafana Alloy sending profiling data to Pyroscope. Refer to [Configure the client to send profiles](/docs/pyroscope/latest/configure-client/) for setup instructions.
  2. **Tracing**: An OpenTelemetry SDK sending trace data to Tempo. Refer to the [OpenTelemetry getting started documentation](https://opentelemetry.io/docs/getting-started/) for setup instructions.
  3. **Span profiling bridge**: A language-specific OpenTelemetry integration package that links profiling data with trace spans. Without this package, traces and profiles are independent signals with no connection between them. Refer to [Link tracing and profiling with span profiles](/docs/pyroscope/latest/configure-client/trace-span-profiles/) for per-language setup instructions.

### Use a basic configuration

To use a basic configuration, follow these steps:

1. In the left menu, select **Connections** > **Data sources**.
2. Select your configured Tempo data source from the **Data source** list.
3. Scroll down to the **Traces to profiles** section.
4. Select a Pyroscope data source in the **Data source** drop-down.
5. Optional: Add one or more tags to use in the query. If left blank, the default values of `service.name` and `service.namespace` are used.
   
   The tags you configure must be present in the spans attributes or resources for a trace-to-profiles 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. In that case, you can remap `service.name` to `service_name`.
6. Select one or more profile types to use in the query. Select the drop-down and choose options from the menu.
   
   The profile type or app must be selected for the query to be valid. Grafana doesn’t show any data if the profile type or app isn’t selected when a query runs.
7. Select **Save and Test**.

If you have configured a Pyroscope data source and no profile data is available or the **Profiles for this span** button and the embedded flame graph isn’t visible, verify that the `pyroscope.profile.id` key-value pair exists in your span tags.

### Configure a custom query

To use a custom query with the configuration, follow these steps:

1. In the left menu, select **Connections** > **Data sources**.
2. Select a configured Tempo data source from the **Data source** list.
3. Scroll down to the **Traces to profiles** section.
4. Select a Pyroscope data source in the **Data source** drop-down.
5. Optional: Choose any tags to use in the query. If left blank, the default values of `service.name` and `service.namespace` are used.
   
   These tags can be used in the custom query with `${__tags}` variable. This variable interpolates the mapped tags as list in an appropriate syntax for the data source. Only tags present in the span are included. Tags that aren’t present are omitted.
   
   You can also configure a name for the tag. Tag names are useful where the tag has dots in the name and the target data source doesn’t allow using dots in labels. For example, you can remap `service.name` to `service_name`. If you don’t map any tags here, you can still use any tag in the query, for example: `method="${__span.tags.method}"`. Learn more about [custom query variables](/docs/grafana/latest/datasources/tempo/configure-tempo-data-source/#custom-query-variables).
6. Select one or more profile types to use in the query. Select the drop-down and choose options from the menu.
7. Switch on **Use custom query** to enter a custom query.
8. Specify a custom query to be used to query profile data. You can use various variables to make that query relevant for current span. The link shows only if all the variables are interpolated with non-empty values to prevent creating an invalid query. You can interpolate the configured tags using the `$__tags` keyword.
9. Select **Save and Test**.

### Configuration options

The following table describes options for configuring your **Trace to profiles** settings:

Expand table

| Setting name     | Description                                                                                                                                                                                                                                                                                                    |
|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Data source      | Defines the target data source. You can select a Pyroscope \[profiling] data source.                                                                                                                                                                                                                           |
| Tags             | Defines the tags to use in the profile query. Default: `cluster`, `hostname`, `namespace`, `pod`, `service.name`, `service.namespace`. You can change the tag name for example to remove dots from the name if they’re not allowed in the target data source. For example, map `http.status` to `http_status`. |
| Profile type     | Defines the profile type to use in the query.                                                                                                                                                                                                                                                                  |
| Use custom query | Toggles use of custom query with interpolation.                                                                                                                                                                                                                                                                |
| Query            | Input to write custom query. Use variable interpolation to customize it with variables from span.                                                                                                                                                                                                              |

## Provisioning

You can provision the trace to profiles configuration using the `tracesToProfiles` block in your data source YAML file. For the full provisioning YAML example including all Tempo settings, refer to [Provision the Tempo data source](/docs/grafana/latest/datasources/tempo/configure-tempo-data-source/provision/).

## Verify the integration

After configuring trace to profiles, verify the integration:

1. Open **Explore** and select your Tempo data source.
2. Run a query to load a trace.
3. Expand a span and confirm that the **Profiles for this span** button appears in the span details.
4. Click the button and verify that an embedded flame graph loads with profiling data.

## Troubleshooting

If trace to profiles links aren’t appearing or the flame graph is empty, refer to [Trace to logs/metrics/profiles issues](/docs/grafana/latest/datasources/tempo/troubleshooting/#trace-to-logsmetricsprofiles-issues) in the troubleshooting guide. For additional diagnosis steps, refer to [Troubleshoot trace to profiles](/docs/pyroscope/latest/configure-client/trace-span-profiles/) in the Pyroscope documentation.

If the configuration fields are greyed out, your data source is provisioned. Refer to the [Provisioning](#provisioning) section for how to update the configuration via YAML.

## Next steps

- [Configure trace to logs correlation](/docs/grafana/latest/datasources/tempo/configure-tempo-data-source/configure-trace-to-logs/): Navigate from spans to related logs in Loki.
- [Configure trace to metrics correlation](/docs/grafana/latest/datasources/tempo/configure-tempo-data-source/configure-trace-to-metrics/): Link spans to metrics queries in Prometheus.
- [Provision the Tempo data source](/docs/grafana/latest/datasources/tempo/configure-tempo-data-source/provision/): Configure the Tempo data source using a YAML file.