Operations | Monitoring | ITSM | DevOps | Cloud

In March, we announced that Grafana OnCall (OSS) had entered maintenance mode. However, OnCall’s development continues in Grafana Cloud as Grafana Cloud IRM, combining on-call management and incident response into one integrated solution. Many users told us they still want to self-host Grafana and rely on Grafana Alerting to detect potential issues early—but they also need to escalate and manage incidents using an incident response management (IRM) solution.

We’re excited to share that Rollbar is now part of the ilert integration catalog! This new technical partnership allows software teams to detect application errors in real time with Rollbar and instantly respond using ilert’s powerful alerting and incident management features.

No matter where or how you work, we all have the same goal when an incident occurs: to get it resolved effectively and efficiently—and as quickly as possible. However, the way we achieve that goal isn’t always the same. We understand that different organizations operate differently, so you need flexibility from your IRM tooling.

Observability platforms want to do it all—from data collection to incident response. Their pitch is appealing: one platform to eliminate context switching and reduce overhead. But when critical systems fail—and they will fail—, add-on incident management modules won’t save you. You need an end-to-end system built specifically for high-stakes incident management.

Why are we still handling IT incident response like it’s 2014? Every day, ITOps teams are flooded with alerts, spread thin across hybrid systems, and stuck trying to stitch together visibility from solutions that don’t talk to each other. The incidents keep coming, but the tools aren’t getting smarter—and the humans are burned out. Even with best practices in place, response is often slow, inconsistent, and reactive. You chase symptoms instead of solving problems.

“By the time a pager alerts you to a problem, it’s too late to think about how to manage the incident.”(Google SRE Workbook) Gett, a global leader in urban mobility and corporate travel tech, knew that relying on its incumbent paging system and siloed manual processes for incident management was no longer sustainable. Any delay in response and service restoration could jeopardize customer satisfaction and business continuity.

Today, I’m excited to share the Internet’s Largest Incident Response Glossary. It’s a collection of over 500 terms covering on-call, alerting, monitoring, and system reliability. It took us over 2 weeks from ideation to completion of this project and in this post, I would like to share how we approached this beast!

When an incident wakes your team early in the morning, the last thing you want is confusion about who’s responding or how help will arrive. An effective on-call schedule doesn’t just get the right person online. It helps them stay calm, confident, and capable of solving problems quickly. Done right, your on-call setup becomes a powerful lever for reducing Mean Time to Acknowledge (MTTA), Mean Time to Resolve (MTTR), and the overall stress that incidents place on your team.

An incident response platform helps organizations manage, track, and resolve IT incidents quickly and efficiently. With the right platform, teams can minimize downtime, reduce the impact of incidents, and improve overall response times. ‍ In this article, we’ll explore the top 5 incident response platforms for 2025, helping you choose the best solution for your needs. ‍