The VictoriaMetrics Observability Blog

We’re participating in three conferences until the end of the year as sponsors and speakers: KubeCon NA, OSMC & OSA Con 2022. This blog outlines our participation at each one of them with details on how to meet us or listen to our talks.

In monitoring, the term cardinality defines the number of unique time series stored in TSDB. The higher is cardinality, the more resources are usually required for metrics processing and querying. Let’s see how Cardinality explorer can help us here.

VictoriaMetrics is a monitoring solution. It was designed to collect and process telemetry from many systems, provide a retrospective view, and forecast metrics for capacity planning. But what about monitoring VictoriaMetrics itself?

Benchmarking VictoriaMetrics and Grafana Mimir on the same hardware

An article about how to remove a storage node from a VictoriaMetrics cluster gracefully

When looking for a most scalable open source time series database, what are the criteria to care about? Read this blog to get our recommendations.

Three examples of vmagent high-availability setup for pull and push models

This is a status update following the statement we made on February 28th 2022 with regards to the war on Ukraine. Our team is safe, our business continues to grow and we’re looking forward to the continued work with our customers and users.

The VictoriaMetrics v1.76 release headlines our first VictoriaMetrics releases roundup blog post, which summarises all the releases we published in the first quarter of 2022; and includes feature highlights such as multi-level downsampling (the most wanted Vicky feature in 2021).

We’ll have to see what would be the cost of serving the same workload at Amazon Managed Service for Prometheus, Google Cloud Managed Service for Prometheus and Managed VictoriaMetrics.