When Does AI Actually Help in Incident Response? Identifying Good First Messages in Cloud Service Incidents
Open Access
- 7 October 2026
- conference paper
- Published by Association for Computing Machinery (ACM)
- p. 2242-2253
Abstract
Modern cloud services increasingly rely on agentic software operations, where AI agents, rule-based automation (monitoring alerts, health checks, template runbooks), and human engineers coordinate incident response through shared discussion threads. As these systems mature, the on-call engineer faces a growing volume of machine-generated messages and must quickly identify which ones actually help, under minutes-level time pressure where every moment spent reading noise delays mitigation. We study this problem across thousands of production incidents from 5 cloud services over four years (2022 to 2026). We define a good first message (GFM): the first machine-generated message in an incident discussion thread whose specific content demonstrably influences the on-call engineer’s next investigation action. Three findings emerge. First, incident threads grew 7× longer (from a median of 4 to 30 messages) as AI agents were introduced, yet noise (messages lacking substantive technical content) decreased: among the three actor types, AI agents, rule-based automation, and humans, AI produces the lowest noise rate. Second, AI agents and automation are complementary, covering different workflow roles (e.g., diagnosis vs. monitoring) rather than duplicating each other. Third, only about one in five incidents contains a GFM; influence varies dramatically by functional role but far less by actor type: what a message says matters more than who posted it. We further show that GFMs can be surfaced automatically: σ-rank, an LLM ranker whose prompt encodes domain knowledge from the empirical study, places the GFM in the top 3 of ∼20 machine messages 89% of the time, reducing the engineer’s noise-reading burden by 7×. These results provide the first empirical evidence of how deployed AI output is actually consumed during live incidents and offer a practical mechanism to cut through information overload in time-critical incident response.Keywords
This publication has 41 references indexed in Scilit:
- Triangle: Empowering Incident Triage with Multi-Agent2025
- How Different are the Cloud Workloads? Characterizing Large-Scale Private and Public Cloud Workloads2023
- Large Language Models for Software Engineering: Survey and Open Problems2023
- CONAN: Diagnosing Batch Failures for Cloud Systems2023
- Newcomer OSS-Candidates: Characterizing Contributions of Novice Developers to GitHubEmpirical Software Engineering, 2022
- An Initial Exploration of the “Good First Issue” Label for Newcomer Developers2021
- Every build you break: developer-oriented assistance for build failure resolutionEmpirical Software Engineering, 2019
- An Empirical Investigation of Incident Triage for Online Service Systems2019
- AIOps: Real-World Challenges and Research Innovations2019
- An Evaluation Study on Log Parsing and Its Use in Log Mining2016