Operations | Monitoring | ITSM | DevOps | Cloud

Learn how to allocate cloud spend, rightsize Kubernetes safely, stop idle resources, manage commitments, and prevent cost spikes without risking reliability.

Modern enterprises no longer operate as isolated systems. Every customer order, supplier commitment, shipment, invoice, and payment relies on information moving seamlessly across a growing network of applications, partners, and business functions. In many SAP-driven organizations, SAP IDocs serve as one of the primary mechanisms for exchanging business information between various SAP and non-SAP systems. Most business users never see them, never interact with them, and often never hear about them.

An effective healthcare network is the IT infrastructure that keeps clinical and operational services reachable, responsive and diagnosable across hospitals, clinics, imaging centers, laboratories, remote sites, cloud services and vendor connections. A device can be up while Electronic Health Record (EHR) access, Picture Archiving and Communication System (PACS) retrieval, telehealth or a wireless clinical workflow is still slow or unavailable.

Network operations teams have heard plenty about AI this year. Most of it answers the alert in front of it, then hands the rest of the incident back to an engineer. Someone still has to correlate the evidence, find the cause, prepare the fix, and prove it held. This week, we announced Selector Foundry, the agentic NetOps solution built into the Selector platform. Foundry adds a team of specialized AI agents on top of the full-stack observability and AIOps foundation our customers already run.

A roadmap for the Telecom, Media, Entertainment, and Gaming industries.

Australia’s critical infrastructure landscape has changed significantly. The Security of Critical Infrastructure Act 2018 (SOCI Act) has evolved from a framework focused primarily on identifying critical assets and reporting incidents into a broader risk-management and operational-resilience regime. The 2024 reforms reinforced that direction, increasing the focus on the systems, data, and technology dependencies that underpin Australia’s essential services.

There is a moment every web user knows by feel. You click a link, read the page, hit Back, and the previous screen is just there. No spinner, no flash of white, no jitter. This is the bfcache (back/forward cache) in action, and for most teams it feels invisible.

When something goes wrong in production, you do not want to spend the first five minutes rearranging charts. You want the error rate, throughput, queue depth, memory, and view metrics that show when customers are having issues while using your app.

At Grafana Labs, observability is what we do. So as we started building AI agents, we naturally reached for the same instincts we bring to every system: measure it, set targets, and make reliability something you can reason about instead of hope for. That instinct led us somewhere unexpectedly useful. It turns out one of the oldest ideas in reliability engineering, the error budget, maps beautifully onto one of the newest problems in software: how do you know if an AI agent is actually any good?

Somewhere in the last year, your team's code output went up. Pull requests are opened faster. The backlog of small fixes and routine changes started clearing quicker than it used to. If delivery still feels roughly as slow as it did before, that's what happens when you speed up one part of a process without touching anything downstream of it.