Menu

Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Documentationbreadcrumb arrow Grafana Tempobreadcrumb arrow Managebreadcrumb arrow Cross-tenant query
Open source

Cross-tenant query federation

Note

You need to enable multitenancy_enabled: true in the cluster for multi-tenant querying to work. Refer to Enable multi-tenancy for more details and implications of multitenancy_enabled: true.

Tempo supports multi-tenant queries for search, search-tags, and trace-by-ID search operations.

To perform multi-tenant queries, send tenant IDs separated by a | character in the X-Scope-OrgID header, for example, foo|bar.

By default, cross-tenant query is enabled and can be controlled using multi_tenant_queries_enabled configuration setting.

yaml 
query_frontend:
   multi_tenant_queries_enabled: true

For more information on configuration options, refer to Enable multitenancy.

TraceQL queries

Queries performed using the cross-tenant configured data source, in either Explore or inside of dashboards, are performed across all the tenants that you specified in the X-Scope-OrgID header.

TraceQL queries that compare multiple spansets may not correctly return all traces in a cross-tenant query. For instance,

{ span.attr1 = "bar" } && { span.attr2 = "foo" }

TraceQL evaluates a contiguously stored trace. If these two conditions are satisfied in separate tenants, then Tempo doesn’t correctly return the trace.