Operations | Monitoring | ITSM | DevOps | Cloud

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?

This discussion is a part of the Basic Series serving as the starting point to quickly get you started with VictoriaMetrics. vmagent is a lightweight metrics collection agent that acts as a bridge between your applications and monitoring storage systems like VictoriaMetrics.

Seeing that VictoriaMetrics products are this popular with engineers worldwide is fantastic: Just a little over a year ago, we hit 10K stars, and with the adoption of VictoriaLogs, the star count now went beyond 14K. We don’t take these GitHub Stars milestones for granted: It’s amazing to see these stats grow organically thanks to the community of users out there who use our products. Thank you so much!