Operations | Monitoring | ITSM | DevOps | Cloud

Why does a checkout or login take several seconds when CPU and memory look normal on every server? In microservices, one click can travel through a long chain of components before the user sees a response. Any one of them can hold the request up, and server graphs won't tell you which. Logs show what each service recorded. Metrics give you averages. What's missing is the path one request took and the place it lost time, and Jaeger tracing records exactly that.

You're investigating checkout errors when someone asks who's coordinating the incident. Support needs an update, and another responder is looking for the runbook. You stop what you're doing to get everyone pointed in the same direction. They're all reasonable requests, but each one takes your attention away from understanding the problem. Yes, your team has a process for handling incidents, but carrying it out is another job for someone who's already busy.

The title is not a joke. For those of you who know Sentry, you know we’ve been giving back to Open Source maintainers since our early days in whatever ways we could. But around five years ago we really started to give in a more meaningful way. This year we increased our budget from $750,000 to $1,000,000.

AppSignal MCP went generally available last month. Until now, adding it to the Claude app meant pasting our endpoint URL into a custom connector form. Now you search for it like any other connector. Open Settings, go to Connectors, select the Discover tab, and search for AppSignal. That's the whole setup. For more detail on each step, follow the Claude app section of the setup guide. It works the same way in Claude on the web and in the desktop app..

What happens when you treat the service grid like a screen. Every now and then a side project starts as one thing and quietly turns into something much sillier. Mine started as a way to get more comfortable with the Icinga 2 configuration. It ended with a question nobody asked: can the service grid in Icinga Web play GIFs? Spoiler: kind of. And on the way, I learned a lot about how Icinga 2, Icinga DB and Icinga Web work together.

You can now retrieve outage reports submitted through your StatusGator status page using our API. Bring user feedback into your internal dashboards, reporting tools, and incident workflows.

Teams often spend as much time preparing information as discussing it: gathering charts, checking business reports, and finding the GitHub activity that explains a change. Every follow-up question can lead to yet another round of work. That's why, as part of ObservabilityCON 2026, we're excited to introduce Grafana Pages, a new feature in Grafana Cloud that gives you a canvas to describe what you need and build a live app in minutes, based on your real data, context, and interactions.