Operations | Monitoring | ITSM | DevOps | Cloud

After a decade of dashboards, alerts, and ever-expanding telemetry pipelines, observability is changing. No longer just the domain of engineering, the most innovative organizations are extending observability to all areas of the business to better understand system behavior, emerging risks, and customer impact. At the same time, rising cloud costs and increasing complexity are forcing organizations to be more intentional about what they observe and why.

Sometimes the most important engineering work starts with a deceptively simple question. Not “What’s the best dashboard layout?” or “How many Ts are in Matt?” (still contested), but something much more fundamental: What if the read path and the write path didn’t have to share the same fate?

You know the situation: You're in a meeting and your alerts start to go off, but no one on the other side of the camera knows why you have to abruptly drop from the call. What if, instead, you had a robot in the background of your Zoom meeting that started to blink when those same alerts went off? You could just point to it, type in the chat "I have to drop," and off you'd go.

Let's talk about being new. Four months ago, I joined Grafana Labs as a senior solutions engineer. It wasn’t just a new company, it was a new industry. I came from the visual workspace provider Miro, where I was comfortable doing discovery and talking about visual collaboration and innovation. But stepping into observability? I was in the deep end. And let me tell you, the imposter syndrome was real. Everyone around me was fluent in this language of metrics, logs, and traces.

Dawid Dębowski is a software engineer at G2A.COM and a Grafana Champion. Holding an MS of Computer Science, Dawid’s main fields of interest related to observability are PromQL and data visualizations using Grafana. If you’ve ever worked with custom metrics in a Prometheus environment, you've probably heard about something called "high cardinality"—or at least I hope you have.

Your users should not be the first to know when your application goes down. When HTTP endpoints fail or respond sluggishly, users experience timeouts, connection errors, and degraded performance — often without clear indication of the root cause. This is where HTTP checks in Grafana Cloud Synthetic Monitoring come in, allowing you to proactively monitor your endpoints, verify they're online, measure response times, and ensure they're returning the correct status codes.