VictoriaMetrics is a time-series database that we use to handle a large volume of metrics coming from our application. We have multiple applications running, and we want to monitor everything to understand exactly what is happening, so we deployed VictoriaMetrics to serve as our time-series database and then use Grafana to visualize the data. VictoriaMetrics serves as a replacement for Prometheus to monitor all the time-series data that comes from our applications.
Monitoring has become more efficient and resource usage has dropped significantly
What is our primary use case?
What is most valuable?
VictoriaMetrics is built with memory constraints in mind, and we saved a significant amount of memory after implementing it. The first advantage is that it is quite easy to use, and we can leverage PromQL queries in VictoriaMetrics with a straightforward deployment process.
The best aspect of using VictoriaMetrics is the reduction in resources including RAM, memory, disk, and other infrastructure requirements, which have all decreased substantially after implementation.
We observed that RAM was reduced by around 70% and disk usage by 75%, while write speed increased 3x and query per second P95 latency became 7x faster. The financial savings are significant because we observed a substantial reduction in resources such as CPU and memory after adopting VictoriaMetrics.
What needs improvement?
VictoriaMetrics is quite a good project and quite easy to use overall, though some documentation could be improved. The main area that needs improvement in VictoriaMetrics is the documentation itself, as the support is adequate and the open-source project does provide replies within one to two days.
For how long have I used the solution?
We have been using VictoriaMetrics for around two years.
What do I think about the stability of the solution?
VictoriaMetrics is stable.
What do I think about the scalability of the solution?
VictoriaMetrics's scalability is quite good.
How are customer service and support?
We use the open-source version of VictoriaMetrics, so we did not require any customer support. However, we do use the open-source project to contact them and learn more about the issues and projects that we are working on.
Which solution did I use previously and why did I switch?
We used Prometheus earlier, but we found that the resource usage was quite high, so we decided to try VictoriaMetrics, which resulted in a substantial reduction in resources.
How was the initial setup?
We did not require any license for VictoriaMetrics since we are using the open-source version, so the setup cost is what we incurred.
What's my experience with pricing, setup cost, and licensing?
We did not require any license for VictoriaMetrics since we are using the open-source version, so the setup cost is what we incurred.
Which other solutions did I evaluate?
Prometheus was the solution we were using, and we did not evaluate other options; we simply proceeded with VictoriaMetrics and have continued to use it.
What other advice do I have?
You should use VictoriaMetrics if you are currently using Prometheus, as I believe it is quite helpful and you should consider switching. I give this review an overall rating of 9.
Which deployment model are you using for this solution?
Public Cloud
