Prometheus monitoring / long-term metric storage
Thanos is a set of components that provides high availability and long-term object-storage capabilities for Prometheus metrics, with a global query view across Prometheus instances.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
Choose for horizontally scalable, multi-tenant Prometheus long-term storage with active Grafana support and remote-write ingestion, despite AGPL-3.0 license.
Grafana Mimir provides horizontally scalable, highly available, multi-tenant, long-term storage for Prometheus.
Choose for a mature, multi-tenant Thanos alternative using remote write, backed by the Cortex community under Apache-2.0.
A horizontally scalable, highly available, multi-tenant, long term Prometheus.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Choose when you want a single or clustered TSDB with high compression and simpler operations, replacing the Thanos component composition.
VictoriaMetrics: fast, cost-effective monitoring solution and time series database
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
Choose when you only need a lightweight aggregating proxy to query multiple Prometheus servers, without long-term storage.
An aggregating proxy to enable HA prometheus
These projects were analysed and named thanos among their alternatives. The relationship is not symmetric — how thanos rates them is a separate judgement, made when thanos is analysed in its own right.
calls thanos “Choose when you already run Prometheus and need multi-cluster long-term storage with object-storage backends rather than a standalone TSDB like VictoriaMetrics.”
VictoriaMetrics: fast, cost-effective monitoring solution and time series database