Enable Grafana Tempo multi-tenancy and configure per-tenant ingestion overrides
domain: grafana.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Set multitenancy_enabled: true (or pass --multitenancy.enabled=true) on every Tempo component so all requests must carry the X-Scope-OrgID header.
Configure ingest clients (OpenTelemetry Collector, Grafana Alloy, or direct OTLP callers) to attach the X-Scope-OrgID header set to the tenant name.
Configure the Tempo data source in Grafana to send the same X-Scope-OrgID header so queries are scoped to the correct tenant.
Point overrides.per_tenant_override_config in the main tempo.yaml at a separate overrides.yaml file to enable per-tenant settings.
In overrides.yaml, set tenant-specific ingestion.rate_limit_bytes, ingestion.burst_size_bytes, ingestion.max_traces_per_user, and global.max_bytes_per_trace, among other fields.
Known gotchas
When you define a per-tenant override, you must set every field you want preserved for that tenant — Tempo replaces unset fields with zero values rather than falling back to the main config's defaults, which can silently zero out retention or limits (e.g. a 0s block_retention).
The overrides file is reloaded dynamically at runtime, so a bad edit takes effect immediately without a Tempo restart.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?