Operations | Monitoring | ITSM | DevOps | Cloud

In today’s hospitals, technology is woven into every touchpoint of patient care. Nurses check vitals through digital monitors. Physicians review test results in the EHR. Medications get ordered, verified, and delivered through a network of connected systems. But when even one link in that chain fails, the impact isn’t just inconvenient—it’s dangerous. Downtime doesn’t just slow operations.

We are proud to announce that Splunk has been named a Leader in the 2025 Gartner Magic Quadrant for Observability Platforms for the third year in a row. In our opinion, our recognition in the Observability category comes on the heels of Splunk being recognized for a tenth consecutive time as a Leader in the 2024 Gartner Magic Quadrant for Security Information and Event Management (SIEM). Splunk was the only vendor named a Leader in both SIEM and Observability for the Gartner Magic Quadrant three times.

You're monitoring a microservices-based system. Alerts trigger when response times exceed 2 seconds. But when you open Jaeger, you're faced with thousands of traces. Identifying which service or operation is responsible becomes time-consuming. Jaeger metrics help reduce this friction by exposing aggregated telemetry. Instead of scanning individual traces, you get service-level and operation-level performance metrics, latency, throughput, and error rates that highlight where the issue lies.

Vertical Pod Autoscaling (VPA) is a component within Kubernetes designed to automatically resize the CPU and memory requests of pods based on their observed, historical usage patterns. While Pepperdata Capacity Optimizer and VPA both change the resource requests of pods in response to changing application resource requirements, there are several key differences.

Arie van den Heuvel is an engineer, a System and Application Management Specialist, and a valued member of our community. Below he has shared his journey using Coroot, and how it has helped improve observability for his team. You can read more of Arie’s writing and support the resource articles he has created for open source on his blog.

In the past year alone, we’ve seen just how much a single outage can disrupt and how much stronger teams become when they learn from it. From the July 16, 2024 incident to the widespread June 2025 outage, it’s clear that incidents are inevitable. The question is: how do you transform each disruption into an opportunity to improve your processes for the next one?

In the cloud, Kafka’s promise of “never lose a byte” quietly morphs into “always pay for two.” Every time the leader syncs followers across zones, you get hit with premium egress charges that can dwarf compute costs. Diskless Kafka turns that upside-down: brokers replicate data straight into S3, so the pricey cross-zone hops vanish. Yes, object storage is slower than a local SSD, but the swap buys you on-demand elasticity and a bill that finally makes sense.

Production AI needs a network that can keep up. Learn why private, scalable connectivity is the key in our webinar recap with Vultr. AI is no longer a proof-of-concept hiding in a developer lab. It’s a full-fledged production workload, and it’s hungry for data. But as enterprises move their AI strategies from theory to reality, they’re hitting a wall that isn’t about algorithms or processing power – it’s about the network.

Kentik transforms real-time network telemetry into actionable alerts for AI-optimized data centers. By converting database queries into custom alerts, engineers can detect issues like elephant flows, idle links, and packet loss before performance suffers and triggers alerts in systems like ServiceNow or PagerDuty.

When our organization – a mid-sized, fast-scaling technology company specializing in enterprise service management solutions, serving clients in regulated industries like finance and healthcare – faced its first serious cybersecurity breach in early 2024, we realized our incident response management approach wasn’t just outdated – it was putting the business at risk. Back then, we had alerts. We had logs.