{"slug": "victoriametrics", "name": "VictoriaMetrics", "category": "observability", "category_name": "Monitoring and analytics", "description": "", "recommenders": 2, "commenters": 5, "warners": 0, "score": 2.429, "rising": -0.65, "first": "2025-11-08", "latest": "2026-08-23", "why": "we migrated from a very expensive Thanos to a VM cluster backed by HDDs, and saved a lot. Performance was much better as well.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 2, "neutral": 3, "compare": 0, "warn": 0}, "spark": [1, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0], "listed": false, "loved": [], "caveat": "", "short_quote": "we migrated from a very expensive Thanos to a VM cluster backed by HDDs, and saved a lot. Performance was much better as well.", "icon": false, "domain": "victoriametrics.com", "github_repo": null, "official_url": "https://victoriametrics.com", "pricing": "", "aliases": ["VictoriaMetrics"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 743902594, "item_id": 46493912, "url": "https://news.ycombinator.com/item?id=46493912", "by": "cadamsdotcom", "date": "2026-01-04", "stance": "recommend", "quote": "add all the metrics and logs one can think of (VictoriaMetrics)", "excerpt": "I have my very fast macbook pro at my desk in my office, and I use tmux and tailscale and git worktrees and I\u2019ve built a notification setup like this author. Thanks to tailscale and ssh I can vibecode on the go from my phone with this setup. While it\u2019s great to leave a task running, no matter what I do I can\u2019t achieve the type of high quality work on the go that I can when I\u2019m sitting at my desk. For me working on a ", "context": "building a SaaS", "use_case": "metrics and logging", "switched_from": "", "story": "Claude Code On-the-Go"}, {"id": 735221520, "item_id": 45951345, "url": "https://news.ycombinator.com/item?id=45951345", "by": "valyala", "date": "2025-11-16", "stance": "recommend", "quote": "VictoriaMetrics is used as a drop-in replacement for Prometheus, Thanos and Mimir.", "excerpt": "> lack of a promise of full PromQL compatibility (too many PromQL dashboards built by too many teams) This is a classical FUD. VictoriaMetrics is used as a drop-in replacement for Prometheus, Thanos and Mimir. It works perfectly across all the existing dashboards in Grafana, and across all the existing recording and alerting rules. I'm unaware of VictoriaMetrics users who hit PromQL compatibility issues during the mi", "context": "", "use_case": "metrics storage", "switched_from": "", "story": "I can't recommend Grafana anymore"}, {"id": 735003712, "item_id": 45937732, "url": "https://news.ycombinator.com/item?id=45937732", "by": "vulkoingim", "date": "2025-11-15", "stance": "recommend", "quote": "we migrated from a very expensive Thanos to a VM cluster backed by HDDs, and saved a lot. Performance was much better as well.", "excerpt": "I'm not sure where you saw that Victoria Metrics uses object storage. It doesn't - it uses block storage and it runs completely fine on HDD, you don't even need SSD/NVMe. There are multiple ways to deal with ingestion floods. Kafka/distributed log is one of them, but it's not the only one. In cluster mode VM is a distributed set of services that scale out independently and buffer at different levels. Resource usage f", "context": "previous job migrated to VM", "use_case": "metrics storage at scale", "switched_from": "Thanos", "story": "I can't recommend Grafana anymore"}]}], "caveats": [], "who": [{"by": "cadamsdotcom", "context": "building a SaaS", "url": "https://news.ycombinator.com/item?id=46493912", "date": "2026-01-04"}, {"by": "vulkoingim", "context": "previous job migrated to VM", "url": "https://news.ycombinator.com/item?id=45937732", "date": "2025-11-15"}], "tags": [], "use_cases": ["metrics collection", "weather metrics storage", "metrics and logging", "metrics storage", "metrics storage at scale", "observability platform"], "compared": [{"slug": "grafana", "name": "Grafana", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "clickhouse", "name": "ClickHouse", "co": 1, "switched_from": 1, "switched_to": 0}, {"slug": "claude", "name": "Claude", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [{"id": 770142160, "item_id": 48133885, "url": "https://news.ycombinator.com/item?id=48133885", "by": "valyala", "date": "2026-05-14", "stance": "recommend", "quote": "VictoriaMetrics is optimized solely for typical observability tasks", "excerpt": "VictoriaMetrics CTO here. We at VictoriaMetrics took another approach. We tried using ClickHouse as a database for metrics in 2017, but then decided implementing a specialized database for metrics. This database uses ClickHouse architecture ideas for achieving the best performance and the lowest resource usage. The main difference between ClickHouse and VictoriaMetrics is that VictoriaMetrics is optimized solely for ", "context": "VictoriaMetrics CTO", "use_case": "metrics database", "switched_from": "ClickHouse", "story": "Traceway: MIT-licensed observability stack you can self-host in ~90s"}], "threads": [{"url": "https://news.ycombinator.com/item?id=45934940", "title": "I can't recommend Grafana anymore", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49391553", "title": "OTel isn\u2019t going well", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48449187", "title": "Ask HN: What are tools you have made for yourself since the advent of AI", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48091898", "title": "Traceway: MIT-licensed observability stack you can self-host in ~90s", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46491486", "title": "Claude Code On-the-Go", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=45856804", "title": "Study identifies weaknesses in how AI systems are evaluated", "mentions": 1}], "sentiment_by_month": {"2025-11": {"neutral": 1, "recommend": 1}, "2025-12": {}, "2026-01": {"recommend": 1}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {"neutral": 1}, "2026-07": {}, "2026-08": {"neutral": 1}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 790484288, "item_id": 49405268, "url": "https://news.ycombinator.com/item?id=49405268", "by": "rtpg", "date": "2026-08-23", "stance": "neutral", "quote": "We use victoriametrics", "excerpt": "We use victoriametrics, but I believe that's just the collector side of it cuz we also query into it with grafana. Datadog isn't just a collector, but the whole querying UI as well, right?", "context": "", "use_case": "metrics collection", "switched_from": "", "story": "OTel isn\u2019t going well"}, {"id": 775269589, "item_id": 48454349, "url": "https://news.ycombinator.com/item?id=48454349", "by": "FireBeyond", "date": "2026-06-08", "stance": "neutral", "quote": "my own VictoriaMetrics / Grafana set up on Kubernetes", "excerpt": "Workflow: Built a meeting-intelligence pipeline that turns raw, error-prone transcripts into a structured, queryable knowledge base. Meetings get auto-transcribed by Krisp, whose speech recognition mangles the things I most need correct, like colleague names, customer names, internal product and architecture terms. I hand each transcript to Claude alongside a hand-built context document, and it works a fixed routine:", "context": "", "use_case": "weather metrics storage", "switched_from": "", "story": "Ask HN: What are tools you have made for yourself since the advent of AI"}, {"id": 743902594, "item_id": 46493912, "url": "https://news.ycombinator.com/item?id=46493912", "by": "cadamsdotcom", "date": "2026-01-04", "stance": "recommend", "quote": "add all the metrics and logs one can think of (VictoriaMetrics)", "excerpt": "I have my very fast macbook pro at my desk in my office, and I use tmux and tailscale and git worktrees and I\u2019ve built a notification setup like this author. Thanks to tailscale and ssh I can vibecode on the go from my phone with this setup. While it\u2019s great to leave a task running, no matter what I do I can\u2019t achieve the type of high quality work on the go that I can when I\u2019m sitting at my desk. For me working on a ", "context": "building a SaaS", "use_case": "metrics and logging", "switched_from": "", "story": "Claude Code On-the-Go"}, {"id": 735221520, "item_id": 45951345, "url": "https://news.ycombinator.com/item?id=45951345", "by": "valyala", "date": "2025-11-16", "stance": "recommend", "quote": "VictoriaMetrics is used as a drop-in replacement for Prometheus, Thanos and Mimir.", "excerpt": "> lack of a promise of full PromQL compatibility (too many PromQL dashboards built by too many teams) This is a classical FUD. VictoriaMetrics is used as a drop-in replacement for Prometheus, Thanos and Mimir. It works perfectly across all the existing dashboards in Grafana, and across all the existing recording and alerting rules. I'm unaware of VictoriaMetrics users who hit PromQL compatibility issues during the mi", "context": "", "use_case": "metrics storage", "switched_from": "", "story": "I can't recommend Grafana anymore"}, {"id": 735003712, "item_id": 45937732, "url": "https://news.ycombinator.com/item?id=45937732", "by": "vulkoingim", "date": "2025-11-15", "stance": "recommend", "quote": "we migrated from a very expensive Thanos to a VM cluster backed by HDDs, and saved a lot. Performance was much better as well.", "excerpt": "I'm not sure where you saw that Victoria Metrics uses object storage. It doesn't - it uses block storage and it runs completely fine on HDD, you don't even need SSD/NVMe. There are multiple ways to deal with ingestion floods. Kafka/distributed log is one of them, but it's not the only one. In cluster mode VM is a distributed set of services that scale out independently and buffer at different levels. Resource usage f", "context": "previous job migrated to VM", "use_case": "metrics storage at scale", "switched_from": "Thanos", "story": "I can't recommend Grafana anymore"}, {"id": 733727891, "item_id": 45857993, "url": "https://news.ycombinator.com/item?id=45857993", "by": "pahae", "date": "2025-11-08", "stance": "neutral", "quote": "I'm currently implementing a full observability platform based on VictoriaMetrics / Victorialogs + Grafana.", "excerpt": "I wish the big providers would offer some sort of trial period where you can evaluate models in a _realistic_ setting yourself (i.e cli tools or IDE integrations). I wouldn't even mind strict limits -- just give me two hours or so of usage and I'd already be happy. Seriously. My use-case is probably pretty far from the usual tasks: I'm currently implementing a full observability platform based on VictoriaMetrics / Vi", "context": "", "use_case": "observability platform", "switched_from": "", "story": "Study identifies weaknesses in how AI systems are evaluated"}]}