In our recent virtual meetup the VictoriaMetrics Founders team discussed some of our Q1 2023 highlights, including features highlights, the 2023 roadmap for VictoriaMetrics as well as first introduction to the upcoming VictoriaLogs. In this blog post, we’d like to share a summary of these highlights and a heads up on where to find our team in the coming weeks and months - starting with our participation at KubeCon Europe 2023.
As many of our users and the wider monitoring community will know, Graphite Query Language is a query language for Graphite monitoring tools, which helps analyze data stored in it. Graphite is a well-known and respected pioneer in the monitoring space, which has seen a number of next generation monitoring solutions enter the scene … such as ourselves. It’s been used by a wide range of companies, which started using monitoring tools more than a decade ago.
Prometheus remote write protocol is used by Prometheus for sending data to remote storage systems such as VictoriaMetrics. See these docs on how to setup Prometheus to send the data to VictoriaMetrics. This protocol is very simple - it writes the collected raw samples into WriteRequest protobuf message, then compresses the message with Snappy compression algorithm and sends it to the remote storage in an HTTTP POST request.
Share: VictoriaMetrics is always improving, with frequent updates adding new features, performance improvements and bug fixes listed at the CHANGELOG page. We usually make at least a single release every month. All the new features and bug fixes go to the latest release. That’s why we recommend periodically upgrading VictoriaMetrics components to the latest available release. But the latest release may also contain bugs in the latest features.
Recording rules is a clever concept introduced by Prometheus for storing results of query expressions in a form of a new time series. It is similar to materialized view and helps to speed up queries by using data pre-computed in advance instead of doing all the hard work on query time. Like materialized views, recording rules are extremely useful when user knows exactly what needs to be pre-computed. For example, a complex panel on Grafana dashboard or SLO objective.
Share: When we posted our first ever Momentum blog about a year ago detailing our 2021 achievements, we were just weeks away from Russia’s renewed attack of Ukraine. While the war isn’t won yet and we’re approaching the one year anniversary of the attack, it’s heartening to see how much has changed around the world and that almost everyone now knows the expression: Slava Ukraini! So if we had to choose one word to best describe 2022 it might be: Resilience.
Share: One of the latest benchmarks we did was for OSMC 2022 talk VictoriaMetrics: scaling to 100 million metrics per second - see the video and slides. While the fact that VictoriaMetrics can handle data ingestion rate at 100 million samples per second for one billion of active time series is newsworthy on its own, the benchmark tool used to generate that kind of load is usually overlooked. This blog post explains the challenges of scaling the prometheus-benchmark tool for generating such a load.
VictoriaMetrics is proud to announce that we consider vmbackup and vmbackupmanager to be feature-complete solutions as of release 1.85.3. These backup components are essential for ensuring the safety and integrity of your data, and we have made a number of improvements in recent releases to make them even more reliable and user-friendly.
In monitoring, the term cardinality defines the number of unique time series stored in a time series database (TSDB). The higher the cardinality, the more resources are usually required for metrics processing and querying.
Share: 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? There is one of the software development approaches called Observability Driven Development (ODD). In a nutshell, it means that developers should always keep in mind that software needs to be transparent to the person who uses it. Does your software make backups?
