Operations | Monitoring | ITSM | DevOps | Cloud

Observability has come a long way from its origins in monitoring logs and metrics. Today, it sits on a maturity curve: Organizations move from fragmented tool stacks to unified platforms to proactive engineering practices that tie reliability to business outcomes. To better understand where IT leaders are on this curve, Grafana Labs surveyed 150 decision-makers across industries in advance of ObservabilityCON 2025.

Your team just deployed to production. The infrastructure spun up in 90 seconds, but recreating your monitoring? That’ll take hours. It’s added late in the process, managed through dashboards, and prone to inconsistency. Short-term, this slows delivery and creates visibility gaps that surface only during incidents. Long-term, it leaves a business-critical capability out of your observability pipeline.

In modern IT systems—distributed services, cloud-native platforms, and dynamic networks—just knowing that something is “up” isn’t enough. Green checkmarks on dashboards don’t tell you why performance shifted, why latency crept in, or why a perfectly healthy-looking service suddenly failed. This is where the conversation around visibility and observability begins. They sound similar, but they solve very different problems.

Your production checkout flow just started returning 500 errors. Six microservices handle checkout. Logs show errors in three of them. Which service broke? Which error happened first? What caused the cascade? Traditional debugging doesn't work. You can't attach a debugger to production. Searching logs across six services gives thousands of lines with no obvious connection. By the time you correlate timestamps and trace IDs manually, customers have abandoned their carts.

The 2025 DORA State of AI-Assisted Software Development Report delivers a critical insight for technology leaders: AI is fundamentally an amplifier, not a solution. It magnifies the strengths of high-performing organizations with robust observability while exposing the dysfunctions of struggling ones. For organizations that have rushed to adopt AI coding assistants all while expecting immediate productivity gains, this finding demands a strategic pivot.

Your checkout flow starts in an AWS Lambda function, calls a payment service running on EKS, then triggers notifications through Azure Functions. Three different compute platforms, two cloud providers, one distributed trace that you can't see. Cloud providers want you to use their native monitoring tools. AWS pushes X-Ray and CloudWatch. Azure promotes Application Insights and Azure Monitor. These tools work well within their ecosystems but lock you into vendor-specific implementations.

IT leaders know the drill. An alert storm rolls in and the tickets pile up. Your team scrambles to piece together root causes before service degradation kicks in. But the firefighting rages on, even when you have enough dashboards, monitoring, and alerts to light up a Christmas tree. Enterprise leaders need to quit burning budget on shiny dashboards that look good in the boardroom but do nothing to stop outages in the real world.