The VictoriaMetrics Observability Blog

VictoriaMetrics is a fast, scalable monitoring system made of modular components like vminsert, vmstorage, and vmselect. It supports both single-node and clustered setups, along with tools for backup, restore, alerting, access control, and data migration. Data can be ingested, stored, queried, backed up, and restored with high performance and minimal resource use.

We have just got back from an incredible weekend representing VictoriaMetrics at LinuxFest Northwest 2025 in beautiful Bellingham, WA! 🌲🏔️

Go applications can implement graceful shutdown by handling termination signals (SIGTERM, SIGINT) via os/signal or signal.NotifyContext. Shutdown must complete within a specified timeout (e.g., Kubernetes’ terminationGracePeriodSeconds)…

In our fourth VictoriaMetrics Tech Talks episode, we wrapped up our deep dive into logs and summarized the key takeaways for effective log management. This installment concluded our log series, featuring Co-founder and CTO Alex who joined to share some exciting news and updates from VictoriaMetrics.

This post recaps the latest VictoriaMetrics Cloud updates, including new organization management features, OpenTelemetry integration, a powerful Explore tab, and expanded API capabilities, making your monitoring experience even more seamless and efficient.

Prometheus querying involves multiple moving parts: functions, operators, modifiers, and subqueries. Small differences in how vectors are handled or rollups are applied can lead to completely different outcomes or errors. MetricsQL extends PromQL by handling these edge cases more gracefully with features like default rollups.

We believe microservices shouldn’t be the default and that companies should start with monoliths until reality actually demands they scale and shift from one node to a cluster of nodes. As a result, we offer clustering on an open source basis because we want to support realistic growth. Read on for details!

When running Go apps in Kubernetes, default CPU thread scheduling can conflict with cgroup CPU limits. The runtime sees all host CPUs, but the container may only be allowed a fraction of one. This often leads to early throttling. Properly configuring GOMAXPROCS avoids this waste and improves stability.

Go’s gRPC implementation uses code generation to create type-safe client and server interfaces. Streaming RPCs allow sending multiple messages over a single connection, perfect for real-time updates and continuous data flows. Interceptors provide middleware-like functionality for authentication, logging, and error handling without modifying your core service logic.

In our third episode, we will guide you through efficiently ingesting and optimizing log pipelines with VictoriaLogs. We’ll provide actionable insights on streamlining your logging processes, enhancing performance, and, most importantly, extracting valuable insights from your data to improve your operations, troubleshoot issues, and gain a competitive edge.