time series database / metrics monitoring
VictoriaMetrics is a fast, cost-effective, Prometheus-compatible time-series database and monitoring backend for large-scale metrics observability.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
Choose Prometheus when you want the canonical upstream monitoring and TSDB ecosystem and do not need VictoriaMetrics' extra long-term storage optimizations or MetricsQL extensions.
The Prometheus monitoring system and time series database.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Choose when you need SQL-powered real-time analytics over high-cardinality event/time-series data instead of a PromQL-centric metrics backend.
ClickHouse® is a real-time analytics database management system
Choose when you need a lightweight, high-throughput Java/SQL TSDB for tick/event data and do not need Prometheus compatibility.
QuestDB is a high performance, open-source, time-series database
Choose when you want a unified columnar engine for metrics, logs, and traces on object storage and can accept a younger, broader observability database.
The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage.
Choose when you need a Kubernetes-native, multi-tenant, horizontally scalable long-term store for Prometheus metrics rather than a single-node-friendly Prometheus backend.
Grafana Mimir provides horizontally scalable, highly available, multi-tenant, long-term storage for Prometheus.
Choose when you need a Kubernetes-native distributed time-series database for metrics and are willing to standardize on its operational model and not necessarily the Prometheus query API.
LinDB is a scalable, high performance, high availability distributed time series database.
Choose when you already run Prometheus and need multi-cluster long-term storage with object-storage backends rather than a standalone TSDB like VictoriaMetrics.
Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
Choose when you want a general-purpose metrics/events datastore with InfluxQL/SQL and do not need PromQL compatibility.
Scalable datastore for metrics, events, and real-time analytics
Choose for Industrial IoT time-series workloads needing a specialized clusater DB with SQL support, rather than Prometheus-centric monitoring storage.
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
Choose when you want PostgreSQL compatibility plus time-series partitioning/compression and prefer SQL over a purpose-built Prometheus storage engine.
A time-series database for high-performance real-time analytics packaged as a Postgres extension
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
An older all-in-one monitoring platform for teams already invested in Open-Falcon that do not require Prometheus ecosystem compatibility.
An open-source and enterprise-level monitoring system.
These projects were analysed and named VictoriaMetrics among their alternatives. The relationship is not symmetric — how VictoriaMetrics rates them is a separate judgement, made when VictoriaMetrics is analysed in its own right.
calls VictoriaMetrics “Drop-in Prometheus-compatible scraper/TSDB/PromQL engine with lower resource usage and optional cluster mode.”
The Prometheus monitoring system and time series database.
calls VictoriaMetrics “When you need a resource-efficient, Prometheus-compatible TSDB with simple single-node or cluster setup and low RAM/CPU usage.”
Scalable datastore for metrics, events, and real-time analytics
calls VictoriaMetrics “Choose if you want a cost-effective, PromQL-compatible monitoring TSDB with high performance and low resource use, not SQL.”
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
calls VictoriaMetrics “Choose VictoriaMetrics when you need a resource-efficient, Prometheus-compatible TSDB that is cheaper to operate in monitoring stacks.”
A time-series database for high-performance real-time analytics packaged as a Postgres extension
calls VictoriaMetrics “Choose when you want a single or clustered TSDB with high compression and simpler operations, replacing the Thanos component composition.”
Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
calls VictoriaMetrics “Choose it for low-cost Prometheus-compatible metrics storage when your workload is monitoring rather than general time-series analytics.”
Apache IoTDB
calls VictoriaMetrics “PromQL-compatible metrics DB component; choose it for a production-proven metrics backend and run VictoriaLogs separately for logs.”
The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage.