VictoriaMetrics can be used as long-term storage for Prometheus or for vmagent. It supports Prometheus querying API, so it can be used as Prometheus drop-in replacement in Grafana. It implements MetricsQL query language, which is backwards compatible with PromQL. VictoriaMetrics provides high performance and good scalability for both inserts and selects. It outperforms InfluxDB and TimescaleDB by up to 20x. Uses 10x less RAM than InfluxDB and up to 7x less RAM than Prometheus, Thanos or Cortex when dealing with millions of unique time series (aka high cardinality). It provides high data compression, so up to 70x more data points may be stored into limited storage comparing to TimescaleDB and up to 7x less storage space is required comparing to Prometheus, Thanos or Cortex. A single-node VictoriaMetrics may substitute moderately sized clusters built with competing solutions such as Thanos, M3DB, Cortex, InfluxDB or TimescaleDB. VictoriaMetrics consists of a single small executable without external dependencies. All the configuration is done via explicit command-line flags with reasonable defaults. All the data is stored in a single directory pointed by -storageDataPath command-line flag. Supports metrics' scraping, ingestion and backfilling via multiple protocols: InfluxDB, Graphite, OpenTSDB, Prometheus, CSV, JSON. Metrics from Prometheus exporters such as node_exporter. See these docs for details. Prometheus remote write API InfluxDB line protocol over HTTP, TCP and UDP. Ideally works with big amounts of time series data from APM, Kubernetes, IoT sensors, connected cars, industrial telemetry, financial data and various Enterprise workloads. Has open source cluster version.