Grafana Enterprise Traces configuration
Grafana Enterprise Traces utilizes a configuration that’s a superset of the Tempo configuration file.
The configuration reference describes configuration options specific to GET.
GET services
You can also configure these GET services:
Cluster query federation. This optional federation-frontend service can aggregate data from multiple GET clusters and tenants in a single query. This service works with searches and TraceQL.
The GET gateway is a service target that proxies requests to other GET microservices. You can also use it for client-side load balancing of requests proxied to the distributors.
OAuth integration. GET supports the OpenID Connect (OIDC) core standard to validate tokens. GET can integrate with an existing OAuth token provider at your organization.
Admin API. The Admin API service manages tenants, access policies, and tokens. Refer to the Admin API and Admin client configuration reference sections for details.
Tokengen. The
tokengenservice generatesadminAPI tokens and stores them in theadminobject storage.
Multi-tenancy
GET enables multi-tenancy by default. All requests require a valid tenant identifier. For more information about how multi-tenancy works, refer to the Tempo multi-tenancy documentation.
GET also supports per-tenant configuration in the metrics-generator through environment variables and per-tenant overrides. Refer to the Multi-tenant support for Metrics-Generator documentation for more information.
