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.

When we first launched Catchpoint’s Internet Resilience Report back in 2024, we were already seeing troubling cracks in the digital foundations of major businesses. Remember the CrowdStrike outage? Fast-forward to this year, and it's clear the stakes have only gotten higher. Google Cloud’s recent outage is yet another reminder of how tightly interwoven the Internet is and how all it takes is for one major player to go down, for thousands of businesses to be affected worldwide.

Modern applications demand strong observability to ensure performance, reliability, and quick troubleshooting. Two powerful open-source tools, OpenTelemetry and Fluent Bit play key roles in this space. While OpenTelemetry offers a full-stack framework for collecting metrics, logs, and traces, Fluent Bit specializes in fast, lightweight log forwarding.

The era of scattered monitoring tools and fragmented operational visibility is over. As hybrid and multi-cloud environments have become the norm rather than the exception, traditional observability approaches—siloed metrics, isolated logs, and disconnected traces—can no longer keep pace with the complexity of modern IT infrastructure. Organizations today need more than just monitoring.

We’ve just rolled out a helpful new setting to give you tighter control over how uptime is measured: Redirect URL Validation.

As infrastructure grows in complexity, the demand for intelligent, autonomous operations is no longer optional. AIOps tools help IT organizations sift through data noise and detect what matters. But insights alone don’t close the loop. Without automation, even the most accurate prediction still relies on humans to triage, decide, and resolve. This is the gap intelligent automation fills.

In Kubernetes environments, cost is rarely just about spend. It’s about performance, node utilization, workload behavior, and how all of those align with your team’s operational goals. Komodor’s approach to cost optimization has an operational advantage due to its deep visibility into your entire Kubernetes estate. Imagine the potential for cost optimization when you have complete visibility into every aspect of your Kubernetes operations.

After four years. Hundreds of meetings and conversations. Countless forms and paperwork submissions… …We’ve done it. SquaredUp is finally, officially B Corp certified We can now say that we are part of a unique global movement – and we couldn’t be more proud, excited, and motivated for our journey ahead.

When using Percepio TraceRecorder, kernel objects like queues, semaphores and mutexes are named using their address by default. This can be a bit hard to follow for complex traces. However, it is quite easy to set more descriptive custom names for your RTOS kernel objects. This by calling the “SetName” functions (or macros) found in the TraceRecorder API, for example: The first argument is the pointer to the object (i.e. the object address).

We've made major improvements to maintenance window notifications with flexible options that adapt to your communication strategy. Now you have three notification options for every maintenance window: You'll also see how many subscribers will be notified with a detailed breakdown of subscriber counts by channel type (Email, Slack, Teams, etc.), giving you complete visibility into your communication reach before sending.