Safe Remediation as Risk-Constrained Intervention Decision in Microservice Systems
Not on the map. Why?
Abstract (arXiv)
In modern IT operations (IT-Ops), the cost of an incorrect repair often exceeds the cost of no action at all. Yet existing automated remediation systems are designed to generate actions rather than to decide whether intervention is warranted, leaving safety as an afterthought enforced by manual approval. This paper makes three contributions to close this gap: (i) we reformulate safe remediation as a risk-constrained intervention decision problem and cast it as a Constrained Markov Decision Process (CMDP), in which the agent maximizes repair success subject to a bounded false remediation rate (FRR); (ii) we introduce a three-dimensional risk decomposition comprising blast radius, reversibility, and epistemic uncertainty, providing operators with an interpretable per-action safety interface; and (iii) we design a context-adaptive human-in-the-loop (HITL) gate that turns escalation from a binary failsafe into a bandwidth-aware control layer responsive to on-call load and business criticality. The full policy is learned offline from historical incident logs, enabling explicit control of the expected FRR. Experiments on the Train Ticket microservice benchmark with Chaos Mesh fault injection and an RCAEval-aligned fault taxonomy show that our framework reduces FRR by 39% while improving repair success by 2.5 points over a strong runbook baseline, and reduces on-call escalation load by 17% relative to a fixed-threshold variant.
Key facts. No citing papers in the map yet (data through 7 Oct 2026). Builds on 7 of its 21 references that are in the map. First posted on arXiv 22 Jul 2026.
Builds on
7 of 21 references.
References · 7
- 2020Conservative Q-Learning for Offline Reinforcement Learningcited by 1,777
- 2017Constrained Policy Optimizationcited by 928
- 2015Recursive Partitioning for Heterogeneous Causal Effectscited by 254
- 2023Automatic Root Cause Analysis via Large Language Models for Cloud Incidentscited by 82
- 2023Recommending Root-Cause and Mitigation Steps for Cloud Incidents using Large Language Modelscited by 38
- 2023Eadro: An End-to-End Troubleshooting Framework for Microservices on Multi-source Datacited by 19
- 2024X-lifecycle Learning for Cloud Incident Management using LLMscited by 19
Built on by
Not cited yet.