Monitoring
Never-firing alerts: What they are and how to deal with them
Read how vmalert helps to find alerting rules which don’t match any time series. Such rules will never fire and only trick users with a false sense of protection.
How to use VictoriaMetrics for monitoring with Netdata Agent
How to set up VictoriaMetrics as long-term storage for Netdata Agent metrics
Save network costs with VictoriaMetrics remote write protocol
Save network bandwidth costs when transferring data to VictoriaMetrics starting from v1.88
Rules backfilling via vmalert
Read how to use vmalert’s replay mode to retroactively evaluate recording and alerting rules with SLO objective as example.
Cardinality explorer
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 Monitoring
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?
How to Choose a Scalable Open Source Time Series Database: The Cost of Scale
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.
vmagent High-Availability Examples
Three examples of vmagent high-availability setup for pull and push models
Pricing comparison for Managed Prometheus
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.
Monitoring Proxmox VE via Managed VictoriaMetrics and vmagent
Monitoring Proxmox hypervisor via VictoriaMetrics, vmagent and built-in metric server