Operations | Monitoring | ITSM | DevOps | Cloud

The obituary for the data center was written too soon. While the cloud dominates today’s IT headlines, traditional infrastructure hasn’t disappeared. It is evolving. Enterprises still rely on data centers for control, compliance, and reliability. However, they are increasingly needing the agility, scalability, and cost visibility that the cloud promises. Cloud managed data center services are bridging this gap.

Organizations are adding GenAI to their current and future architectures and product roadmaps, requiring Ops teams to ensure LLMs are accurate, fast, secure and cost-efficient. LLM observability tools directly addresses these needs, helping identify and prevent common LLM errors and issues: LLM observability provides the telemetry data for this analysis. LLM observability tools trace requests end-to-end, evaluate outputs, and correlate quality with latency, cost, prompts, tools, and data sources.

I have begun to truly embrace vibe coding over the last few months, using Cursor as my main code editor and Claude Sonnet 4 for my agent's LLM. It's an exciting time as a developer, we get to experiment with something that promises to 100x our productivity while pioneering the new workflows and strategies for implementing these tools. But, as most people who have done any extensive development with LLMs in a sufficiently sized code base knows, it's a bit like trying to herd scared cats.

Today at ObservabilityCON 2025 in London, we unveiled a number of exciting announcements and updates to Grafana Cloud that reimagine SaaS economics, simplify the complexity of running your observability stack at scale, and provide AI tooling that’s actually useful. (Root cause analysis via chatbot? Yes, please!) Check out the keynote to learn more about how we’re helping you do more with the open observability cloud, and read on for a quick recap of all the news from ObservabilityCON 2025.

When an incident lands in your lap, you’ll often start with a lot of questions: Why is latency so high? What’s causing this outage? How much money are we losing at this very moment? The uncertainty—and the pressure to quickly find answers—has always been one of the more nerve wracking parts of being an on-call engineer, but it doesn’t have to be that way any more.

When it comes to observability, more data doesn’t always mean more clarity. In fact, as telemetry volumes grow, it only becomes more difficult to discern the signals from the noise and to keep overall costs in check. This is exactly why we built Adaptive Telemetry, a suite of features in Grafana Cloud that analyzes how your telemetry is used and then automatically recommends actions like aggregating, sampling, dropping, or reducing low-value data.

Distributed tracing is an essential technique for monitoring modern, cloud-native applications. It provides a holistic view of a request's entire journey as it propagates through a multi-service architecture, making it invaluable for performance optimization and root cause analysis. But how do you generate and collect this trace data in a standardized, vendor-agnostic way? That's where OpenTelemetry comes in.