Metraipolis › archive › dc_d326cf613395

ARGUS: MCP-Grounded Root Cause Analysis for Kubernetes Incidents — arXiv:2608.23084

Source
arXiv (en)
Original
https://arxiv.org/abs/2608.23084
License (as archived)
CC0-1.0
Archived
2026-10-18T08:12:40.788Z
SHA-256 of the archived text
e4ba699dc943aacc288dfd83b977790e5f1e5ffbd7c96c972071f191c03cce96
Stable URL of this page
https://metraipolis.com/documento/dc_d326cf613395

How to cite

ARGUS: MCP-Grounded Root Cause Analysis for Kubernetes Incidents — arXiv:2608.23084 — arXiv (en), https://arxiv.org/abs/2608.23084 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_d326cf613395 (Metraipolis archive dc_d326cf613395, sha256 e4ba699dc943aacc288dfd83b977790e5f1e5ffbd7c96c972071f191c03cce96)
BibTeX
@misc{dcd326cf613395,
  title = {ARGUS: MCP-Grounded Root Cause Analysis for Kubernetes Incidents — arXiv:2608.23084},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2608.23084},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_d326cf613395; sha256 e4ba699dc943aacc288dfd83b977790e5f1e5ffbd7c96c972071f191c03cce96},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2608.23084. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Kubernetes incident triage requires correlating signals from metrics, logs, container state, and messaging systems across multiple monitoring tools, a fragmented workflow that slows diagnosis and contributes to alert fatigue. Large language models (LLMs) have shown promise for automated root cause analysis (RCA), but existing systems rely on custom, system-specific data access layers that cannot be reused across organisations. We present ARGUS, an MCP-grounded RCA assistant that connects a commercial LLM to live Kubernetes observability data through standardised MCP servers covering Kubernetes state, Prometheus metrics, Loki logs, and NATS messaging, and delivers structured diagnostic summaries inside the Slack incident channel where on-call engineers already work. We conduct a preliminary evaluation of ARGUS using three complementary methods: controlled fault injection across ten Kubernetes incident scenarios, rubric-based scoring of the resulting RCA summaries on three dimensions, and semi-structured interviews with six on-call engineers at an industrial partner. ARGUS named the correct root cause in all ten scenarios with an aggregate MCP success ratio of 0.91. Practitioners trusted the diagnostic output but consistently expressed scepticism toward the recommended fixes. Our central finding is a diagnostic/prescriptive asymmetry: ARGUS reliably identifies what went wrong, but is perceived as less reliable or trustworthy at specifying what to do next. This pattern can be observed across all three evaluation methods, and has important implications for future autonomous agentic incident handling systems.

Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-08-25 in cs.SE).
Categorie arXiv: Software Engineering (cs.SE).
Pagina del lavoro: https://arxiv.org/abs/2608.23084 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-18T08:07:33.015Z dalla pagina https://arxiv.org/catchup/cs.SE/2026-08-25?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).