Repository navigation
Different tenants want different block retention #6195
|
I want to set for different tenants different block retention. Is it even possible? |
Replies: 3 comments
|
You can do this through per tenant overrides. Notice that the block retention is different for the two tenants. Be careful to set every field when using per tenant overrides of Tempo will override unset fields with 0s. main config: overrides.yaml: |
|
Great example. I've added this to the docs: #6570 |
|
Per-tenant retention is a real gap in distributed tracing — it's surprisingly common to have compliance requirements that differ by service or customer. The approaches that work today with Tempo: Object storage TTL per bucket prefix Caveat: the TTL applies at block level, not at trace level. A block that contains traces from 30 days ago AND yesterday won't be deleted until all traces in it are past the TTL. Block size/duration affects how granular this gets. Multiple Tempo deployments per tenant tier Route at the gateway level based on tenant ID. Operationally more complex but gives clean isolation. Works well if you have a small number of distinct retention tiers rather than fully arbitrary per-tenant retention. Tempo's native per-tenant override Upvoting the feature request if you haven't already is probably the most direct path to getting this into the roadmap. What's driving the different retention requirements — compliance, cost, or SLA differences? |
You can do this through per tenant overrides. Notice that the block retention is different for the two tenants. Be careful to set every field when using per tenant overrides of Tempo will override unset fields with 0s.
main config:
overrides.yaml: