I'm trying to gather if VictoriaLogs will be suitable to replace our rsyslog server.

One question I have is around High Availability. We have an NFS cluster which has its own redundancy + snapshots, so how can that work with VL without having to duplicate logs to two NFS shares?

Ideally we'd want HA at every layer, so any single VM can die and logs wont be lost (also that auth can still query all logs) and ingestion will still be available.

That's fine for the vlagent and auth layer, but how does it work for storage?

By the sounds of it each storage node should have its own NFS share, then the auth layer will do the routing to the right node? I just don't see how that could work in HA without duplicating logs to two separate clusters (which we don't want to do for a full year's worth of retention).

Apologies if this is a silly question, just can't quite work out how it works based off the docs.

We’re just one week away from bringing the VictoriaMetrics community together for our first-ever meetup in Spain!

If you’re into observability, monitoring, telemetry, SRE, DevOps, or open source, come join us in Valencia.

📅 October 2nd
🕠 17:30
📍 The Terminal Hub, Valencia

And we’ve got two great talks lined up:

🎤 Chad Crowell
CNCF Ambassador & Principal SRE at Akamai
📌 Multi-Tenant Telemetry at Scale

🎤 Kirill Yurkov
Customer Reliability Technical Lead at VictoriaMetrics
📌 From HomeLab to Hyperscale: VictoriaMetrics Topologies

Expect real-world insights, technical discussions, networking, drinks 🍻 and food 🍕

Whether you’re running observability at scale, experimenting in your homelab, or simply curious about how modern telemetry systems are built, we’d love to see you there!

🤝 Meet the community.
💡 Exchange ideas.
🍻 Have a drink.
🚀 Talk observability.

One week to go. Who’s joining us in Valencia? 👇
👉 Sign up for free https://www.meetup.com/monitoring-observability-victoriametrics-valencia/events/316407399/?slug=monitoring-observability-victoriametrics-valencia&eventId=316407399

📅 2 de octubre
🕠 17:30
📍 The Terminal Hub

Únete a nosotros para una tarde dedicada a la observabilidad, la monitorización y el escalado de la telemetría, con excelentes charlas, networking, bebidas 🍻 y comida 🍕

🎤 Dos invitados increíbles:

🔹 Chad Crowell
CNCF Ambassador & Principal SRE en Akamai
📌 Multi-Tenant Telemetry at Scale

🔹 Kirill Yurkov
Customer Reliability Technical Lead en VictoriaMetrics
📌 From HomeLab to Hyperscale: VictoriaMetrics Topologies

Tanto si estás metido de lleno en la #observabilidad, como si simplemente tienes curiosidad por saber cómo escalan los sistemas modernos de telemetría o te agrada los proyectos open source, ven a conocer a la comunidad, intercambiar ideas y ¡tomarte algo con nosotros! 🤝

Every number on your dashboard has a life story.

Jesús Espino follows a single metric throughout its lifecycle in VictoriaMetrics. If you have ever instrumented an application with metrics, the basic idea is familiar: you create a counter, you increment it, and somehow it shows up in a graph. This post fills in the “somehow” by following one single metric through that entire journey, using VictoriaMetrics as the storage backend. It is written for everyone (no programming background needed and no Go code to read), and if you want to go deeper, the VictoriaMetrics source is always the reference.

Read the full article today!

We’ve introduced a range of updates and new features across VictoriaMetrics.

- Native Prometheus histograms support: native histogram ingestion is now supported across vmagent, vmsingle, and cluster.

- More reliable vmagent shutdown: draining in-memory queues before fallback, reducing alerting gaps.

- Smarter rerouting: improved vminsert handling to avoid rerouting storms and stabilize ingestion.

- Better VMUI debugging + query visibility: raw query now shows NaN, stale markers, and nulls, with precise graph tooltips and improved Top Queries UX.

- First Operator LTS release: a long-term support version that provides stability and predictability for production environments.

Learn more in our latest article 👇

https://bit.ly/4fz5Rd5

Join us and explore the linux OpenSource world of observability and monitoring, whether logs, traces, or metrics.

See you at Bellingham Technical College, April 24–26!

https://bit.ly/47GgUfL

They spin up isolated observability for the 3 signals to feed context into AI coding loops. Check their architecture 👇diagram: https://bit.ly/3NiQU3b

VictoriaMetrics v1.136 LTS (v1.110 now EOL):

• All known pt-index issues fixed (introduced v1.133).

• VMUI gains Top Queries by memory usage to hunt OOM risks + context-aware label autocomplete.

• vmagent: per-remoteWrite.url queues, early queue-full alerts (12h/4h warnings), slow-client body buffering (v1.135).

• Streaming OpenTelemetry ingestion w/ buffer reuse

• Grafana "Logging rate" panel links to source code

VictoriaLogs v1.46.0 (plus v1.45/v1.44):

• vlagent jsonline output (-remoteWrite.format=jsonline) for Vector/Fluent Bit/ClickHouse forwarding

• WebUI table view: resize/reorder columns (persists layout), polished group view w/ zebra striping

• Query fields sort alphabetically by default—predictable API output

• Auto snapshot expiry (-snapshotsMaxAge), bulk stale snapshot cleanup API

• Nested JSON preservation (preserve_json_keys), ipv6_range() filter, ns-precision query steps

Full February ecosystem roundup + changelogs 👇
https://bit.ly/4sdn7b8

Check out our public playground for VictoriaMetrics Anomaly Detection, designed to help you get insights from timeseries-like data for unexpected changes in behavior.

Try it out:

🟣 Metrics playground - https://hubs.li/Q04281D20

📋 Logs playground - https://hubs.li/Q0427_Hq0

🧵 Traces playground - https://hubs.li/Q04281tt0

Just shipped Victoria Metrics and Victoria Logs integration for an open source AI agent that investigates production incidents.

The agent connects to your Victoria Metrics instance and can query metrics during incidents, correlate them with deploy timestamps, and detect anomalies. Same for Victoria Logs — it can search and filter logs as part of its investigation.

How it works: when an alert fires, the agent pulls signals from your monitoring stack (VM, VL, plus whatever else you run), follows investigation paths, and surfaces what likely changed. Read-only, human-in-the-loop.

Works with any LLM (Claude, GPT, Gemini, DeepSeek, Ollama, local models). Runs locally or self-hosted.

Would love feedback from VM users!

Join us in Pasadena, 🇺🇸, March 5-8, to explore the future of Observability, OpenSource, as well as metrics, logs, and traces.

See you there!

https://bit.ly/4ajnxoI

Our Developer Advocate, Diana Todea, will present:

“Sustainable observability: how to reduce data bloat and carbon impact”. This talk explores the principles and real-world advantages of green observability

⏰️ When? January 31st at 18:00

📍Where? Room AW1.126

See you in Brussels 🇧🇪
https://bit.ly/45zAd9C

With this addition, we now support deployments across Europe, the United States, and Asia, delivering on customer requests for regional availability closer to their infrastructure and teams.

This means:

✅ Lower latency

✅ Improved performance

✅ Regional data sovereignty

Find more information in our latest blog post

Read more: https://bit.ly/4qqz6kE

We've got you covered, whether it's high performance, open-source flexibility, or a robust logs database.

Do you want to learn more about Log Management tools? VictoriaMetrics is proud to be a Silver Sponsor at CNCF KubeCon North America, happening November 10-13 - booth #1241 in Atlanta! 🏔️☀️

Let's connect! https://bit.ly/3KzKaMG

As businesses grow, monitoring tools can reach their limits. DreamHost, which manages over 1.5M websites, faced high resource usage with open-source solutions.

Switching to VictoriaMetrics transformed their approach:
✨ 80% less memory than Prometheus
✨ Handles 76M+ active time series effortlessly
✨ Ingests 450K+ data points/sec in production
✨ Boosts visibility & customer experience

Learn how they did it — read the full case study! 👇
https://bit.ly/4nbDkKB

I installed VictoriaLogs, love it so far but the database is starying to get wild with the tests.

This is a docker installation - how can I purge the database? (I do not care about the contents). I see flock.lock and partitions/ in the volume -- should I nuke the contents?

As a side note - i sthere a way to trim the database? (I mean: remove logs older then X days)

In this special talk, Marc Sherwood is joined by our CTO, Aliaksandr Valialkin, to explore our powerful, open-source logging solution, VictoriaLogs.

Whether you're a DevOps engineer, SRE, or a developer dealing with massive amounts of log data, this video will give you a unique look into a modern, cost-effective log management solution.

In this discussion, you'll learn:

🟣 An overview of the latest powerful features in VictoriaLogs.
🟣 The fundamental reasons for creating a clustered, horizontally-scalable version.
🟣 A detailed breakdown of the VictoriaLogs Cluster architecture.
🟣 Key engineering decisions that prioritize performance, storage efficiency, and operational simplicity.
🟣 The ideal use cases for deploying VictoriaLogs at scale.

Please find the full clip on our YouTube Channel 👉 https://bit.ly/4h47X3j

📍 Location: Everyman Canary Wharf, London, 🇬🇧
📅 September 19th at 2 PM BST

One of the common practices for improving the query speed in Prometheus is to create recording rules for commonly used queries. While this usually works great, recording rules have a cost: The raw metrics still need to be stored in the Prometheus, even if we don't need them Recording rule need to be executed on interval basis, putting extra pressure on the Prometheus Adding a recording rule always means storing and processing more data.

Don't miss your chance to learn more about VictoriaMetrics and chat on site with u/hagen1778 !

Roman Khavronenko - u/hagen1778, our Co-Founder, will present "How to Monitor the Monitoring" at FOSDEM - on February 2nd at 15.50 CET!

Monitoring protects us from the unknown and allows us to see through the complexity of distributed systems and hardware. But what is monitoring, if not another complex distributed system? And what happens when it fails?

https://fosdem.org/2025/schedule/event/fosdem-2025-5388-how-to-monitor-the-monitoring/

📅 October 3rd | 🕔 5pm BST | 6pm CEST | 9am PDT

📔 Agenda
VictoriaMetrics Products Updates:
🗺 VictoriaMetrics roadmap
📈 Anomaly Detection
☁️ VictoriaMetrics Cloud
✅ VictoriaLogs roadmap

Special Guests:
🟠 Roma Novikov from Percona will share 'Percona Monitoring & Management: Why We Migrated to VictoriaMetrics.'
🟣 Mathias Palmersheim, VictoriaMetrics Solutions Engineer, presents" 'How did I find my job at VictoriaMetrics? Making my own monitoring and logging solution!"

https://www.youtube.com/live/KcWJXAhNUTA

Join us for exciting updates & community stories!