{"slug":"best-time-series-databases-for-high-cardinality-observability-metrics","title":"Best time-series databases for high-cardinality observability metrics","question":"What are the best time-series databases for high-cardinality observability metrics in 2026?","verdict":"As of 2026-09-04, Claude, Gemini and Grok collectively rank VictoriaMetrics #1 for time-series databases for high-cardinality observability metrics on ModelsAgree by aggregate score. The models' case: Purpose-built merge-tree architecture handles extreme label cardinality and rapid series churn without the memory bloat of traditional inverted indexes, delivering. The models' main caveat: Cluster mode lacks automated shard rebalancing during scaling, requiring manual partition management, and it is strictly optimized for time-series. The strongest alternative is ClickHouse — Column-store with exceptional compression and query speed that handles wide, high-cardinality label sets without the index blowup that hurts. Not unanimous: Claude picks ClickHouse. Source: https://modelsagree.com/best/best-time-series-databases-for-high-cardinality-observability-metrics (modelsagree.com, CC BY 4.0).","category":"Database","url":"https://modelsagree.com/best/best-time-series-databases-for-high-cardinality-observability-metrics","updated":"2026-09-04","models":["Claude","Gemini","Grok"],"consensus":"2 of 3 models rank VictoriaMetrics the top pick","disagreement":"Claude picks ClickHouse","combined":[{"rank":1,"product":"VictoriaMetrics","domain":"victoriametrics.com","score":14,"appearances":3,"modelRanks":{"Claude":2,"Gemini":1,"Grok":1},"reason":"Purpose-built merge-tree architecture handles extreme label cardinality and rapid series churn without the memory bloat of traditional inverted indexes, delivering industry-leading RAM/CPU efficiency, single-binary operational simplicity, and full PromQL/MetricsQL compatibility."},{"rank":2,"product":"ClickHouse","domain":"clickhouse.com","score":12,"appearances":3,"modelRanks":{"Claude":1,"Gemini":2,"Grok":3},"reason":"Column-store with exceptional compression and query speed that handles wide, high-cardinality label sets without the index blowup that hurts inverted-index TSDBs; scales horizontally, backs many commercial observability platforms (e.g. it underpins products from Signoz and others), and is genuinely open-source with a huge community and SQL access for ad-hoc analysis. Assumes the team can invest in schema/ingestion design rather than wanting turnkey metrics."},{"rank":3,"product":"Grafana Mimir","domain":"grafana.com","score":10,"appearances":3,"modelRanks":{"Claude":3,"Gemini":3,"Grok":2},"reason":"The scale-out multi-tenant PromQL backend when one VM cluster is not enough: object storage as primary, query sharding, strong tenant isolation, and the path Grafana Cloud itself runs. Wins when a platform team must serve many orgs at hundreds of millions of series with long retention. Near-tie with ClickHouse if you are willing to leave PromQL."},{"rank":4,"product":"Amazon Timestream","domain":"amazon.com","score":2,"appearances":1,"modelRanks":{"Claude":4},"reason":"InfluxDB 3.x's rebuild on Apache Arrow/DataFusion/Parquet (FDAP stack) directly targets the old cardinality ceiling, giving columnar storage, SQL, and cheap object-storage retention; a credible managed path for teams already in the Influx ecosystem or wanting a hosted engine."},{"rank":5,"product":"Chronosphere","domain":"chronosphere.io","score":2,"appearances":1,"modelRanks":{"Grok":4},"reason":"The commercial answer when cardinality is already a cost and reliability crisis: control plane shapes, aggregates, and drops series before persist (Uber M3 lineage), so the bill and query path stay bounded without asking every team to stop emitting labels."},{"rank":6,"product":"InfluxDB","domain":"influxdata.com","score":2,"appearances":1,"modelRanks":{"Gemini":4},"reason":"Architected from scratch on Apache Arrow, DataFusion, and Parquet (IOx engine), effectively eliminating the catastrophic series-key index limits of earlier InfluxDB versions and enabling performant SQL-native querying on top-tier cloud object storage."},{"rank":7,"product":"Datadog","domain":"datadoghq.com","score":1,"appearances":1,"modelRanks":{"Claude":5},"reason":"For teams that want zero infrastructure ownership, Datadog ingests high-cardinality metrics and offers best-in-class UI, correlation across metrics/traces/logs, and alerting; it removes the operational burden entirely and is proven at very large scale."},{"rank":8,"product":"GreptimeDB","domain":"greptime.com","score":1,"appearances":1,"modelRanks":{"Grok":5},"reason":"Object-storage-native columnar engine with PromQL + SQL on one model; v1.0 GA in 2026 and Flat SST built specifically for millions of series (published ~4× write / ~10× query vs the old per-series layout). Credible if you want PromQL without Mimir’s component count and a path to logs/traces in the same engine."},{"rank":9,"product":"Thanos","domain":null,"score":1,"appearances":1,"modelRanks":{"Gemini":5},"reason":"Provides a seamless, non-disruptive pathway to achieve global metric querying and cost-effective long-term retention over object storage without replacing existing edge Prometheus instances."}],"perModel":{"Claude":[{"rank":1,"product":"ClickHouse","reason":"Column-store with exceptional compression and query speed that handles wide, high-cardinality label sets without the index blowup that hurts inverted-index TSDBs; scales horizontally, backs many commercial observability platforms (e.g. it underpins products from Signoz and others), and is genuinely open-source with a huge community and SQL access for ad-hoc analysis. Assumes the team can invest in schema/ingestion design rather than wanting turnkey metrics.","fix":"Not a purpose-built metrics TSDB — no native PromQL, downsampling, or retention tiers out of the box, so you build the observability layer (or adopt one) yourself; operationally heavier than a drop-in Prometheus store."},{"rank":2,"product":"VictoriaMetrics","reason":"Purpose-built for exactly this problem — its design tolerates high-cardinality and churny label sets far better than vanilla Prometheus/Thanos, with low memory footprint, strong compression, fast MetricsQL/PromQL, and a simple single-binary or clustered deploy. Open-source core with a paid enterprise tier competing on equal footing; excellent cost-per-series.","fix":"Cardinality is tamed, not free — truly unbounded/exploding label sets still need limits and cardinality explorer discipline; smaller ecosystem than Prometheus proper and some features gated behind enterprise."},{"rank":3,"product":"Grafana Mimir","reason":"Horizontally scalable, Prometheus-compatible backend built to run billions of active series across a cluster with tenant isolation, sharded compactors, and object-storage-backed long-term retention; the strongest choice when you need a massively multi-tenant, HA Prometheus at organization scale.","fix":"Operationally complex (microservices, object store, many components) and resource-hungry — overkill and costly to run for small/medium teams; per-series cost is higher than VictoriaMetrics for equivalent load."},{"rank":4,"product":"Amazon Timestream","reason":"InfluxDB 3.x's rebuild on Apache Arrow/DataFusion/Parquet (FDAP stack) directly targets the old cardinality ceiling, giving columnar storage, SQL, and cheap object-storage retention; a credible managed path for teams already in the Influx ecosystem or wanting a hosted engine.","fix":"The 3.x line is still maturing versus the battle-tested 1.x/2.x many shops run, and feature/operational parity and self-managed options vary by edition — migration and lock-in risk for existing deployments."},{"rank":5,"product":"Datadog","reason":"For teams that want zero infrastructure ownership, Datadog ingests high-cardinality metrics and offers best-in-class UI, correlation across metrics/traces/logs, and alerting; it removes the operational burden entirely and is proven at very large scale.","fix":"Cost is the defining trap — high-cardinality (especially custom metrics and tag combinations) drives bills up steeply, and you're fully locked into a proprietary SaaS with no self-host option."}],"Gemini":[{"rank":1,"product":"VictoriaMetrics","reason":"Purpose-built merge-tree architecture handles extreme label cardinality and rapid series churn without the memory bloat of traditional inverted indexes, delivering industry-leading RAM/CPU efficiency, single-binary operational simplicity, and full PromQL/MetricsQL compatibility.","fix":"Cluster mode lacks automated shard rebalancing during scaling, requiring manual partition management, and it is strictly optimized for time-series metrics rather than general-purpose analytics."},{"rank":2,"product":"ClickHouse","reason":"Unmatched columnar vectorized scan throughput and compression that bypasses traditional TSDB index walls entirely, effortlessly slicing across millions of ad-hoc tag combinations; near-tie with VictoriaMetrics for engineering teams seeking a unified backend for metrics, traces, and logs.","fix":"Steep operational and schema-modeling complexity, requiring custom aggregation engines or proxy translation layers due to the lack of native PromQL semantics out of the box."},{"rank":3,"product":"Grafana Mimir","reason":"The enterprise standard for massive-scale Prometheus environments, delivering battle-tested multi-tenancy, high availability, seamless Grafana ecosystem integration, and cost-effective object-storage persistence that decouples storage growth from compute.","fix":"Substantial operational footprint requiring management of an intricate microservices topology (distributors, ingesters, store-gateways, compactors) with heavy memory baselines during ingest ring rebalancing."},{"rank":4,"product":"InfluxDB","reason":"Architected from scratch on Apache Arrow, DataFusion, and Parquet (IOx engine), effectively eliminating the catastrophic series-key index limits of earlier InfluxDB versions and enabling performant SQL-native querying on top-tier cloud object storage.","fix":"Carries baggage from past breaking architectural shifts across versions, and its PromQL compatibility and Prometheus ecosystem integration remain less mature than dedicated Prometheus-native storage layers."},{"rank":5,"product":"Thanos","reason":"Provides a seamless, non-disruptive pathway to achieve global metric querying and cost-effective long-term retention over object storage without replacing existing edge Prometheus instances.","fix":"Decentralized querying and deduplication across high-cardinality series churn create severe memory spikes and latency bottlenecks on Thanos Querier and Store Gateway components."}],"Grok":[{"rank":1,"product":"VictoriaMetrics","reason":"Best default for the typical Prometheus/Grafana practitioner who hit cardinality walls: remote-write drop-in, MetricsQL, ~4–10× less RAM and ~7–10× better compression than Prometheus, production deployments routinely at tens of millions to 100M+ active series with a single binary then a small shared-nothing cluster. Assumption that shaped rank: most teams need working PromQL dashboards/alerts and lower hardware cost, not a new data model.","fix":"Still series-identity at write time, so unbounded labels (userid, requestid) still punish you; OSS cluster is local-disk first, not S3-native, and MetricsQL is not bit-identical to upstream PromQL."},{"rank":2,"product":"Grafana Mimir","reason":"The scale-out multi-tenant PromQL backend when one VM cluster is not enough: object storage as primary, query sharding, strong tenant isolation, and the path Grafana Cloud itself runs. Wins when a platform team must serve many orgs at hundreds of millions of series with long retention. Near-tie with ClickHouse if you are willing to leave PromQL.","fix":"Heavy microservice ops surface; cost still tracks series count, so it is the wrong first move for a single-team shop that can stay on VictoriaMetrics."},{"rank":3,"product":"ClickHouse","reason":"Architecturally strongest for true high cardinality: a high-card column (traceid, customerid) is just another compressed column, not a new series object. Proven at Tesla/Mercado Libre-class volume, unmatched compression and GROUP BY, and by mid-2026 TimeSeries + experimental PromQL/ClickStack close the metrics gap.","fix":"Not a drop-in metrics store yet — PromQL/rate/counter-reset semantics were still unfinished as of Aug 2026, and a bad ORDER BY or wide GROUP BY fails at query time weeks later. Not for teams that refuse to remodel or rewrite alerts."},{"rank":4,"product":"Chronosphere","reason":"The commercial answer when cardinality is already a cost and reliability crisis: control plane shapes, aggregates, and drops series before persist (Uber M3 lineage), so the bill and query path stay bounded without asking every team to stop emitting labels.","fix":"Closed, sales-priced platform — not an owned TSDB. Not for teams that can still discipline labels and run OSS."},{"rank":5,"product":"GreptimeDB","reason":"Object-storage-native columnar engine with PromQL + SQL on one model; v1.0 GA in 2026 and Flat SST built specifically for millions of series (published ~4× write / ~10× query vs the old per-series layout). Credible if you want PromQL without Mimir’s component count and a path to logs/traces in the same engine.","fix":"Thin production track record versus VictoriaMetrics/Mimir/ClickHouse for mission-critical 100M-series alerting; still a younger bet."}]},"missedByModel":{"Claude":[{"product":"Thanos","reason":"solid Prometheus long-term storage and global query, but weaker high-cardinality handling and higher operational overhead than Mimir/VictoriaMetrics for the same goal"},{"product":"TimescaleDB","reason":"excellent Postgres-based time-series with SQL, but its row-oriented/relational model is less suited to extreme label cardinality than the columnar options above"}],"Gemini":[{"product":"TimescaleDB","reason":"relational strengths and full SQL power are unmatched, but chunk index sizes and ingestion overhead struggle under the extreme ephemeral label churn typical of cloud-native microservices"},{"product":"GreptimeDB","reason":"impressive modern Arrow-based distributed architecture, but lacks the decade of hyperscale production hardening and battle-tested operational tooling of the top 5"}],"Grok":[{"product":"InfluxDB 3","reason":"cardinality ceiling is gone with Arrow/Parquet, but three query-language rewrites and a weaker Prometheus ops ecosystem make it an IoT/SQL store first"},{"product":"TimescaleDB/Tiger Data","reason":"best when you need Postgres joins and SQL analytics, not max series density or PromQL-native alerting"}]}}