Skip to main content
TrustRadius
VictoriaMetrics Community

VictoriaMetrics Community

Overview

What is VictoriaMetrics Community?

VictoriaMetrics is a high-performance monitoring solution and time series database

Read more
Recent Reviews
Read all reviews

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Product Details

What is VictoriaMetrics Community?

VictoriaMetrics is a high-performance monitoring solution and time series database

VictoriaMetrics Community Features

  • Supported: Integrates with existing monitoring solutions - Prometheus, InfluxDB, Graphite, OpenTSDB, Grafana
  • Supported: Query language optimized for typical queries over time series data - MetricsQL

VictoriaMetrics Community Integrations

VictoriaMetrics Community Competitors

VictoriaMetrics Community Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Linux, Mac
Mobile ApplicationNo

VictoriaMetrics Community Customer Size Distribution

Consumers0%
Small Businesses (1-50 employees)10%
Mid-Size Companies (51-500 employees)30%
Enterprises (more than 500 employees)60%
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(3)

Reviews

(1-2 of 2)
Companies can't remove reviews or game the system. Here's why
October 30, 2023

Easy Monitoring solution

Mayank Bansal | TrustRadius Reviewer
Mayank Bansal
SRE
Adidas (Apparel & Fashion, 10,001+ employees)
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We are using VictoriaMetrics for alerting and monitoring purpose along with Prometheus alertmanager. We have configured VictoriaMetrics to pull data from alertmanager and then configure opsgenie APi key to send notification to end stakeholders. it has been helping teams at wide scale to get real time alert and not miss any outage.
Pros and Cons
  • Easy to configure and manage
  • Ready to be configured at cloud and microservices
  • Easy to scale vertically and horizontally
  • Sometimes scaling it becomes costly due to it's high abstact storage capacity at each node
  • very poor GUI
  • We faced issue with IPv6
Likelihood to Recommend
1. It is well suited when you need to monitor large scale of metrics as compared to Prometheus it is faster,more reliable and can provide you metric for more retention period.
2. Uses less resource to run application , can easily be containerised
3. It supports both push and pull models and can be intergated with multiple alerting systems
Most Important Features
  • Scalability
  • Reliability
  • Supports both MetricQL and PromQL so can be integrated with multiple solutions
Return on Investment
  • It was easy to configure and was ready on day1 due to it's less complexity
  • it was easy to configure with pager duty and opsgenie for alerting
  • easily adopted by SRe team and has very simple learning curve
Alternatives Considered
Prometheus only support PromQL and it is very complex with different exporter required for different requirement like Windowsexporter,linixexporter,sqlexporter etc but VictoriaMetrics is very simple comapred to it. VictoriaMetrics support both PromQL and MetricQL and can be integrated with Graphana easily. It is very easy to setup and learn compared to mutiple Prometheus exporters
Other Software Used
October 30, 2023

Better Alternative for Prometheus

Verified User
Engineer in Engineering
Health, Wellness and Fitness Company, 201-500 employees
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
VictoriaMetrics is used for storing and parsing several metrics which is a TimeSeries data. We track multiple metrics majorly related to K8s clusters, namespaces, pod level metrics, Kafka Topic monitoring, broker monitoring, and health of systems, also have some custom metrics pushed from micrometer. Custom metrics could be used by developers as well as business people to determine certain state of the system as well as the product, such as the number of orders being placed from each pin code.
Pros and Cons
  • Easily scalable
  • Less resource intensive compared to other competitors
  • Efficient in query performance as well as data influx
  • Interoperable with Prometheus plugins and queries
  • Community and Eco system -> Although it supports the ecosystem of Prometheus, it is still troublesome for someone who's not using Prometheus
  • Configuration is not so easy, especially if you are a beginner, you will struggle a bit. Even the documentation is not so welcoming for beginners
  • Built-in Visualisation is bare minimal, leading almost everyone to use some other extension/tool
Likelihood to Recommend
Best suited, where your data is highly cardinal since it does a better job at maintaining it than other competitors. It is also well suited if you are using Prometheus and are looking for something that is less hungry for resources in comparison since the migration would be easier. But in case the company is small and wants a solution which is cheap and relies on built-in visualizations, it is not something that is suited. Although it takes fewer resources than Prometheus, it is still resource-intensive and attracts a high cost for maintenance.
Most Important Features
  • Supports Prometheus ecosystem and query language
  • Cheaper than Prometheus in terms of resources
  • Built-in availability features
  • Efficient storage structure
Return on Investment
  • Lowered our infra costs in comparison with our older tools
  • Need minimal effort for migration since it already supports Prometheus ecosystem
  • Saved on Storage costs
Alternatives Considered
Victoria metrics is cheaper and more efficient than Prometheus, in terms of data ingestions, hardware resources, and Storage mechanism, also supports Prometheus extensions, and query language by default. Although Prometheus has a larger community and support, because of the interoperability of Victoria metrics the difference wouldn't concern us much. At the same time, it made our migration simpler
Return to navigation