Operations | Monitoring | ITSM | DevOps | Cloud

Many security teams are looking to move off Splunk, whether to reduce licensing costs, consolidate their SIEM, or take advantage of Google SecOps' built-in threat intelligence and YARA-L detection capabilities. But migrations aren’t easy, and no one wants to run blind while they evaluate and move to a new platform. With OpenTelemetry and Bindplane, you can easily make the switch to SecOps without impacting your existing stack.

How do you make search faster, smarter, and more scalable? During our recent webinar, I sat down with Luke Patterson, senior product manager at WP Engine, and Delphin Barankanira, independent software vendor partner engineering lead and data & AI specialist at Google Cloud, to answer that question. We dug into the mechanics behind WP Engine’s ability to deliver near-instant updates to over 2 million users.

Most platform and observability teams have logs they know are noise. These could be throwaway health check logs, forgotten DEBUG logs, or verbose INFO logs from little used services that only serve to inflate your bill. Regardless of what they contain and why they're there in the first place, the hard part is getting rid of them. Centralized teams want to easily and quickly prevent these logs from being ingested, without having to work with toilsome infrastructure change management to do so.

Your version and deploy health data no longer lives on separate pages. Versions and Deploys are now Dashboard cards, visible by default the next time you open Rollbar. Errors, versions, and deploys in one view, no more tab-hopping to piece together release health.

TL;DR: Attribute. More information on one event gives us more correlation power. It’s also cheaper. When you want to add some information to your tracing telemetry, you could emit a log, create a span, or add a piece of data to your current span. Adding a piece of data to your current span is the best! Usually.

Modern distributed systems fail in ways that can bypass even well-designed isolation patterns. When a failure is actively propagating across services at four in the morning, the question shifts from “how do we limit the blast radius” to “how do we confirm what it actually is.” Monitoring shows which services are in the impact zone, but it cannot show what code path caused the failure to spread, or whether it has stopped.

For IT professionals evaluating Observability for large, complex enterprise environments, the shortlist usually starts with technical depth and ends with operational reality.

On May 5, 2026, a major.de outage disrupted access to websites across Germany and Europe. The incident, caused by a failure at DENIC, the operator of the.de top-level domain, resulted in widespread DNS resolution failures. This was not a typical service outage. It was a failure at the DNS layer that made entire domains unreachable. As DNS caches expired, more services went offline, creating the appearance of a spreading outage across unrelated companies.

NEW + FREE Community Management Packs for Enhanced Monitoring.