Operations | Monitoring | ITSM | DevOps | Cloud

In this session, Jacky Leybman from PagerDuty and David Lotan Bolotnikoff from Logz.io showcase how PagerDuty and Logz.io combine generative AI with rich historical context to automate root cause analysis and accelerate incident response. By correlating real-time telemetry with prior incidents and runbooks, teams reduce manual toil and MTTR while maintaining human-in-the-loop oversight and transparent reasoning.

With the Opsgenie end-of-life deadline (April 5, 2027) fast approaching, you're facing a critical choice: Do you truly need to move your dedicated Incident Response workflow into the complexity of Jira Service Management (JSM) or Compass? If your current process is a reactive treadmill—plagued by alert fatigue, lost context, and constant non-critical paging—the mandated move risks replacing one chaotic toolset with another complex ITSM solution. View this not as a burden, but as a chance to build a standardized, human-centric workflow that solves your biggest pain points and transforms your response from chaos to control.