---
title: "Configure | Grafana Enterprise Traces documentation"
description: "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."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Grafana Enterprise Traces configuration

Grafana Enterprise Traces utilizes a configuration that’s a superset of the [Tempo configuration file](/docs/tempo/v2.8.x/configuration/).

The [configuration reference](/docs/enterprise-traces/latest/configure/reference/) describes configuration options specific to GET.

## GET services

You can also configure these GET services:

- [**Cluster query federation**](/docs/enterprise-traces/latest/configure/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**](/docs/enterprise-traces/latest/configure/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**](/docs/enterprise-traces/latest/configure/integrate-oauth/). 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**](/docs/enterprise-traces/latest/configure/reference/#admin_api_config). The Admin API service manages tenants, access policies, and tokens. Refer to the [Admin API](/docs/enterprise-traces/latest/configure/reference/#admin_api_config) and [Admin client](/docs/enterprise-traces/latest/configure/reference/#admin_client_config) configuration reference sections for details.
- [**Tokengen**](/docs/enterprise-traces/latest/configure/tokengen/). The `tokengen` service generates `admin` API tokens and stores them in the `admin` object 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](/docs/tempo/v2.8.x/operations/multitenancy/).

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](/docs/enterprise-traces/latest/configure/multitenant-metrics-generator/) documentation for more information.