mirror of
https://github.com/awesome-foss/awesome-sysadmin.git
synced 2026-05-06 10:29:07 -05:00
[PR #720] [MERGED] Add VictoriaMetrics to Metrics & Metric Collection #5847
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/awesome-foss/awesome-sysadmin/pull/720
Author: @matthewvaishnav
Created: 3/24/2026
Status: ✅ Merged
Merged: 3/26/2026
Merged by: @Technetium1
Base:
master← Head:add-victoriametrics📝 Commits (2)
ee647beAdd VictoriaMetrics to Metrics & Metric Collectionb89ef67fix: add required blank spacing after VictoriaMetrics entry📊 Changes
1 file changed (+3 additions, -0 deletions)
View changed files
📝
README.md(+3 -0)📄 Description
Hi maintainers, hope you're doing well!
I noticed VictoriaMetrics is missing from the Metrics & Metric Collection section and thought it'd be a great addition. It's one of the most widely used tools in the Prometheus ecosystem — 16,500+ stars, production deployments at Grammarly, Roblox, Spotify and others, and it's a single binary with no external dependencies which sysadmins tend to love.
Worth noting: VictoriaMetrics does have an Enterprise tier with a separate license, but both the single-node and cluster community editions are fully Apache-2.0 with no feature-gating on the core functionality.
Why is it awesome?
VictoriaMetrics is one of the most widely deployed open-source time series databases in the Prometheus ecosystem. It offers significantly better performance and compression than vanilla Prometheus, supports PromQL natively, and ships as a single binary with zero external dependencies — making it extremely straightforward to operate.
Have you used it? For how long?
Yes, approximately one year.
Is this in a personal or professional setup?
Both homelab monitoring and professional infrastructure observability.
How many devices/users/services/... do you manage with it?
Scraping metrics from ~20 services and infrastructure nodes.
Biggest pros/cons compared to other solutions?
Pros: dramatically lower memory and disk usage compared to Prometheus, single binary, fully PromQL-compatible, excellent documentation. Cons: the clustering mode and some advanced features are enterprise-only, though
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.