Operations | Monitoring | ITSM | DevOps | Cloud

VictoriaLogs Practical Ingestion Guide for Message, Time and Streams This VictoriaLogs article serves as a quick way to grasp the core concepts of VictoriaLogs. It covers only the most important information from the documentation, along with common cases identified after troubleshooting many real-world scenarios. If you’re just getting started with VictoriaLogs, this is a great place to begin. For more in-depth or advanced details, refer to the official documentation.

Q2 2025 has brought another wave of improvements to VictoriaMetrics Cloud! If you tuned in to our latest Quarterly Virtual Meetup, you saw firsthand how we’re making observability even more accessible, powerful, and interactive.

VictoriaMetrics introduces FIPS 140-3 compatible builds for its components, starting with version 1.117.0. These builds utilize Google’s FIPS 140-3 validated BoringCrypto module. This is critical for customers in regulated environments (federal government, finance, healthcare) to meet FIPS 140-3 cryptographic requirements for data encryption, TLS, and secure communications.

You asked, and we listened! We’re thrilled to announce the release of the VictoriaLogs Cluster version – one of the most requested and anticipated updates from our user community. This marks a significant leap forward for VictoriaLogs, empowering users to handle log volumes and ingestion rates far beyond the limits of a single node.

VictoriaMetrics Cloud continues to evolve as the most efficient, scalable and open platform in the observability landscape. In our last Q1 update blogpost, we shared new features such as seamless OpenTelemetry integrations, new Organizations support, and improvements in the Explore UI and APIs. This time we wanted to take a minute to showcase how we’re taking the interoperability journey very seriously. Integrations in VictoriaMetrics Cloud Haven’t tried VictoriaMetrics Cloud yet?