From the article
VictoriaMetrics Observability Blog
Author
- Adam Yates
- Aditya Kulkarni
- Adrian Bridgwater
- Agustín Gallego
- Alex Woodie
- Alexander Marshalov
- Aliaksandr Valialkin
- Aman Agarwal
- Antoine Tardif
- Antony Savvas
- Artem Navoiev
- Artur Minchukov
- Bill Tanner
- Cer6erus
- Claudio Masolo
- Cuong Le
- Daniil Romashov
- David Marshall
- David Rubinstein
- 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.
Category
- 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: Observability
Blog posts
Introducing VictoriaStack: The Right Database for Every Signal
Announcing the launch of VictoriaStack, an open-source observability stack that brings VictoriaMetrics, VictoriaLogs, and VictoriaTraces together as one coordinated system. Each signal gets a purpose-built engine while all three share the same deployment model and OpenTelemetry ingestion path. Run one, two, or all three.
VictoriaMetrics Is Expanding in North America
VictoriaMetrics Expands in North America as Spotify and MongoDB Use Our Open-Source Stack to Run Observability at Scale
What's New in VictoriaMetrics Cloud Q3 2026? VictoriaTraces, a Revamped Overview and Monitoring, Alerting for Logs and Traces, and a new Beta coming soon
Q3 2026 brought VictoriaTraces to VictoriaMetrics Cloud, completing the stack with metrics, logs and traces. We also revamped the Overview and Monitoring pages for full transparency, added alerting for logs and traces, enabled stream aggregation for VictoriaMetrics Single, and announced code-named project Visum: our upcoming visualization tool.
VictoriaLogs Has Now a Long Term Support (LTS) Release
VictoriaLogs v1.52.1 is our first Long Term Support release. Enterprise users get 12 months of guaranteed security and bug fix backports, with no new features or breaking changes.
VictoriaMetrics September 2026 Ecosystem Updates
September release roundup brings new releases across the VictoriaMetrics ecosystem, plus the launch of VictoriaTraces in Cloud, completing our managed observability offering of metrics, logs, and traces stack.
The Year-2 Price Cliff: What Your Observability Stack Really Costs Over 3 Years
Why aggressive year-1 discounts in observability often lead to 2–3x renewal bills, plus a simple 3-year TCO framework and five questions to ask before signing.
VictoriaTraces in VictoriaMetrics Cloud: Complete Observability is Here
Announcing VictoriaTraces in VictoriaMetrics Cloud: managed distributed tracing with native OpenTelemetry support, LogsQL for powerful trace analysis, and integrations with Grafana and Jaeger for complete observability, offering predictable pricing and operational simplicity without the overhead of managing a tracing backend yourself.
VictoriaMetrics August 2026 Ecosystem Updates
The VictoriaMetrics team shipped two core releases with important security fixes. The vmanomaly team shipped two updates with improved scaling and more efficient models. Plus, Tech Talks are back, this time demoing AI-assisted incident troubleshooting.
The Life of a Metric
Follow a single metric through its whole life inside VictoriaMetrics: born as a counter in your process, exported over the wire, given an identity and an inverted-index entry, written through an LSM tree, compressed into columnar blocks on disk, read back by a rate() query, downsampled as it ages, and finally deleted when retention runs out.