Multiverse of Thanos: Making Thanos Multi-Tenanted
summary
Thanos now supports centralized multi-tenancy: the receive component provisions per-tenant TSDB and uploads tenant-labeled blocks to S3, with routing via hash rings and regex match; request-level controls enforce request-level limits (byte size, series, samples, active series) to prevent noisy neighbors. A new query flag enables query-path enforcement using prom-label-proxy, producing tenant-specific metrics (query result size buckets, store cache usage) for billing and debugging. Thanos assumes headers are authoritative so an external proxy must handle authentication and header injection.
AI-written summary · about
chapters (5)
related talks
39mAbsorbing Thanos Infinite Powers for Multi-Cluster Telemetry
36mRunning the Observability As a Service For Your Teams With Thanos
27mThanos: Highly Available, Pluggable, Long Term Metric Storage for Everyone!
32mAdopting Thanos Gradually Across All of LastPass Infrastructures
27mWe Stopped Thanos from Snapping $100K from Infra
27mHow Thanos Almost Snapped $100,000 from Our Infra Budget
25mMulti-Cluster Observability: What you need to survive with a fleet
33mStory of Correlation: Integrating Thanos Metrics with Observabi...