Vmselect

vmselect is the query-processing component of the VictoriaMetrics time-series database cluster.

  • Tools & Utilities
vmselect is the query-processing component of the VictoriaMetrics time-series database cluster. It receives queries from monitoring tools, fetches the matching time series from all vmstorage nodes, and merges them into a single result for dashboards and reports. Use it when your VictoriaMetrics deployment runs in cluster mode and you need scalable, distributed query handling.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 2 days ago
Popular
8518,138 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
18,138
Open issues
786
Last commit
2026-11-19
Latest release
v1.156.0
License
Apache-2.0
Activity
steady

Checked 2 days ago - source: GitHub (VictoriaMetrics/VictoriaMetrics)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Cluster components vmselect is one of three independently scalable components in the VictoriaMetrics cluster: vminsert accepts incoming data and routes it to vmstorage nodes, vmselect receives queries and merges results from all vmstorage nodes, and vmstorage stores the time series data. Deploy vminsert, vmselect, and vmstorage together for a working cluster. source

Fetched 42 days ago - each note links to its source

Alternatives (9)

  • Amazon CloudWatch - Amazon CloudWatch is a monitoring service for AWS cloud resources and the applications running on AWS.
  • Better Stack - AI-driven monitoring platform providing incident management, real-time logs, uptime, traces, error tracking, infrastructure analytics, and…
  • Datadog - Datadog Agent is an on-host monitoring agent that collects metrics, logs, and traces from hosts, containers, and Kubernetes clusters and se…
  • Nagios - Nagios is an open-source monitoring system that checks hosts, network services, and IT infrastructure resources so IT administrators can id…
  • Netdata - Netdata is a real-time performance and health monitoring solution that collects per-second metrics from your servers, containers, networks,…
  • Prometheus - Prometheus is a systems and service monitoring system.
  • Splunk - Splunk is a self-hosted platform for collecting, indexing, searching, and analyzing log and security data, helping homelabbers and operatio…
  • TimescaleDB - TimescaleDB is an open-source PostgreSQL extension that turns a standard PostgreSQL database into a high-performance store for time-series…
  • Zabbix - Zabbix is an enterprise-class, open-source distributed monitoring solution designed to monitor the performance and availability of network…

Checked 40 days ago - source: AlternativeTo

Common questions

How does vmselect handle MetricsQL queries in a VictoriaMetrics cluster?

vmselect is the query processing component in cluster deployments. It handles MetricsQL queries and coordinates data retrieval from storage nodes.

Can vmselect return partial results when one storage group is unavailable?

There is a reported bug where vmselect returns HTTP 503 instead of a partial response when a single storage group is unavailable, even when partial responses are allowed.

What may cause a sudden memory usage spike in vmselect?

A reported issue shows the request rate can remain stable during the spike, so the cause is not necessarily increased query volume. A specific query pattern is suspected, but it may be hard to identify from logs or metrics.

Answers sourced from deepwiki.com, github.com, github.com

Community

Collected 48 days ago - public community threads