VictoriaMetrics Cloud: Prometheus & OpenTelemetry metrics and logs logo

    VictoriaMetrics Cloud: Prometheus & OpenTelemetry metrics and logs

    Managed observability platform to deploy and run VictoriaMetrics and VictoriaLogs. Enterprise-ready monitoring and alerting solutions for infrastructure and application IT workloads. VictoriaMetrics Cloud provides cost-efficient time series and logging databases built on scalable open-source monitoring solutions, with added enterprise features (downsampling, retention filters). Guided integrations with Kubernetes, Grafana, Perses, Prometheus, OpenTelemetry, AWS CloudWatch, Fluentbit and more. Support from VictoriaMetrics engineers.

    Ratings and reviews

    4.7
    4 ratings
    4 star
    3 star
    2 star
    1 star
    100%
    0%
    0%
    0%
    0%
    0 AWS reviews
    |
    4 external reviews
    External reviews are from G2  and PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (4)
    reviewer2813076

    Monitoring has become more efficient and resource usage has dropped significantly

    Reviewed on May 30, 2026
    Review provided by PeerSpot

    What is our primary use case?

    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.

    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.

    Computer Software

    A great option for the time se

    Reviewed on Jun 12, 2025
    Review provided by G2
    What do you like best about the product?
    Very fast to access the time series data , I can query, filter and visualize large data quickly
    What do you dislike about the product?
    GUI is not up to the mark . The charts displayed in UI are very basic and difficult to follow.
    What problems is the product solving and how is that benefiting you?
    It solved problems to access the time series data and visualization using Grafana . Previous to VM we used RDBMS which is different to manager or query.
    Telecommunications

    Working in production

    Reviewed on Nov 03, 2022
    Review provided by G2
    What do you like best about the product?
    We are using victora metrices in select insert and storage
    What do you dislike about the product?
    Nothing honeslty we are happy with the product
    What problems is the product solving and how is that benefiting you?
    We are facing issue with Prometheus so victoria metrics helped us a lot
    Denys H.

    It's a nice Prometheus or Influx stack replacement.

    Reviewed on Apr 22, 2021
    Review provided by G2
    What do you like best about the product?
    I think that is the best monitoring stack for IoT from open source that gives you a chance to use a cluster or single node server on different platforms with old or new devices like HDD or SSD disks.
    What do you dislike about the product?
    Some features are only for the enterprise version of VictriaMetrics.
    What problems is the product solving and how is that benefiting you?
    It reduced resource consumption in my installations. For IoT, it's the main feature.