From the article
Monitoring - Insights from VictoriaMetrics
Author
- Adam Yates
- Aditya Kulkarni
- Adrian Bridgwater
- AgustĂn Gallego
- Alex Woodie
- Alexander Marshalov
- Aliaksandr Valialkin
- Aman Agarwal
- Antony Savvas
- Artem Navoiev
- Bill Tanner
- Cer6erus
- Claudio Masolo
- David Marshall
- Denys Holius
- Derek Foster
- Diana Todea
- Dima Lazerka
- Dmytro Kozlov
- Emily Foster
- Fintech Herald
- Fred Navruzov
- Gary Flood
- Gonzalo GarcĂa Labat
- Ivan Yatskevich
- Jaime Hampton
- Jan Sokol
- Jason Bloomberg
- Jason English
- Jean-Jerome Schmidt-Soisson
- JesĂşs Espino
- Joab Jackson
- John Seekins
- Jose Gomez-Selles
- Julien Menan
- Karan Virdi
- Laveesh Kocher
- Leigh McGowran
- Lindsay Clark
- Marc Sherwood
- Mark Baker
- Martijn Van Best
- Martin Veitch
- Mathias Palmersheim
- Michelle Sebek
- Nick Gibson
- Nikolay Khramchikhin
- Pablo Fernandez
- Phuong Le
- Rafal Szypulka
- Renato Losio
- Richard Speed
- Roman Khavronenko
- Vadim Alekseev
- Vadim Rutkovsky
- Yurii Kravets
- Zakhar Bessarab
- Zhu Jiekun
No matching authors found.
Monitoring
- Benchmark
- Community
- Company News
- Customer Stories
- Developer Experience
- Distributed Tracing
- Events
- Go
- Go @ VictoriaMetrics
- High Cardinality
- Kubernetes
- Monitoring
- Observability
- Open Source Tech
- OpenTelemetry
- OTLP
- Performance
- PostgreSQL
- Product News
- Tech Talk
- Time Series Database
- VictoriaLogs
- VictoriaMetrics
- VictoriaTraces
No matching categories found.
Filter: Monitoring
Blog posts
Vibe coding tools observability with VictoriaMetrics Stack and OpenTelemetry
Learn how to add observability to Vibe Coding Tools using OpenTelemetry and the VictoriaMetrics Stack. This guide explains how to configure popular vibe coding tools to export their metrics telemetry and get insights about your vibe coding sessions.
VictoriaMetrics 2025 Developer Experience: A Year in Review
In 2025, VictoriaMetrics deepened its commitment to open source, community, and developer experience across the global cloud-native ecosystem. This year-in-review reflects on key observability themes, global engagement, OpenTelemetry contributions, and the people and conversations that shaped the year.
AI Agents Observability with OpenTelemetry and the VictoriaMetrics Stack
Learn how to add observability to AI agents using OpenTelemetry and the VictoriaMetrics Stack. This guide explains how to instrument popular LLM frameworks and visualize metrics, logs, and traces in Grafana.
Full-Stack Observability with VictoriaMetrics in the OTel Demo
The OpenTelemetry Astronomy Shop demo has long served as a reference environment for exploring observability in distributed systems, but until now it shipped with only a Prometheus datasource. VictoriaMetrics forked the demo and extended it with VictoriaMetrics, VictoriaLogs, and VictoriaTraces, providing insights into VictoriaMetrics’ observability stack where metrics, logs, and traces flow into a unified backend.
Alerting Best Practices
Proper alerting is an art. It is all about foreseeing bad scenarios before they happen, so you can prepare for them. In this article, we go through practical recommendations of approaching the alerting to reduce alerting fatigue and avoid false positives.
vmagent: Key Features Explained in Under 15 Minutes
vmagent is a lightweight agent for collecting and forwarding metrics to remote storage. It supports relabeling, sharding, replication, aggregation, deduplication, and disk buffering to ensure reliable and efficient metric delivery.
VictoriaMetrics Components: Getting Started
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.
Prometheus Monitoring: Functions, Subqueries, Operators, and Modifiers
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.
Don’t default to microservices: You’ll thank us later!
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!