- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes KETriage, a knowledge-enhanced agentic framework for cloud incident triage. It constructs a Hierarchical Symbolic Knowledge Base (HSKB) from historical incidents, organized into ontology, instance, and case layers. During online triage, the agent performs terminology alignment, knowledge retrieval, and concurrent incident filtering, then identifies the responsible service based on current failure evidence, upstream responsibility boundaries, and fault propagation relationships. After incidents are resolved, confirmed historical experience is incorporated into the knowledge base. Experiments on 804 real-world industrial incidents show that KETriage achieves 79.48% Acc@1 and 93.66% Acc@3, outperforming several existing baselines.
Critical strengths
S1. Hierarchical knowledge organization and evidence-constrained attribution are well suited to cross-service incident triage. HSKB connects service dependencies, failure patterns, and historical cases while distinguishing current incident evidence from historical knowledge. This helps avoid attributing responsibility based solely on similar past incidents. The design is particularly useful for cross-service incidents, where KETriage achieves 74.36% Acc@3, compared with 62.56% for TRIANGLE.
S2. The experimental results on real-world industrial incidents are encouraging. The paper evaluates 804 real-world incidents and includes component ablations, knowledge evolution experiments, execution cost comparisons, and error analysis. In particular, the full system reduces average execution time from 679.79 seconds to 190.08 seconds compared with the w/o HC variant, which directly accesses raw evidence. This suggests that structured knowledge can reduce redundant retrieval and reasoning overhead for the agent.
Critical weaknesses
W1. Key implementation details of knowledge construction, retrieval, and updating are missing. Section 3 mainly describes the method through abstract functions such as Retrieve, Filter, and Update. It does not clearly explain how ontology properties are induced, how entities and relations are extracted, how local knowledge is retrieved and expanded, or how new knowledge is merged with existing knowledge and conflicts are handled. Although the paper defines the F/B/D constraints, their implementation and the ranking of candidates that satisfy these constraints are not described in sufficient detail for reproduction. These steps are central to the system's performance.
W2. The experiments do not sufficiently isolate the contributions of hierarchical knowledge organization and knowledge evolution. The ablations in Table 1 demonstrate the overall benefit of HSKB, but there is no direct comparison with flat RAG under the same model, evidence, and computational budget. For knowledge evolution, Figure 3 mainly shows performance changes as more historical knowledge is added to a fixed test set. This does not establish whether the system can reliably adapt to changing service dependencies, conflicting knowledge, or outdated information. In addition, the overall Acc@1 improvement over DeepTriage is only 2.12 percentage points, and no statistical significance analysis is provided.
Questions for authors
Q1. How are HSKB construction and online retrieval implemented?
Could the authors clarify how entities and relations are extracted, how terminology is aligned, how knowledge segments are retrieved and expanded, and how the F/B/D checks and candidate ranking are performed? In particular, how does the agent decide which graph nodes and historical cases to retrieve, and when to stop retrieving?
Q2. How much of the improvement comes specifically from hierarchical knowledge organization rather than conventional RAG?
Could the authors compare flat RAG and a service-dependency-only graph under the same LLM, raw evidence, and computational budget? The distinction between w/o HSKB and w/o HC also needs clarification to determine whether the gains come from knowledge structure or differences in how evidence is accessed.
Q3. Can knowledge evolution adapt to changing service relationships rather than simply accumulating historical cases?
How does the system update or revise existing knowledge when new incident records conflict with established service dependencies or failure patterns? Could the authors evaluate scenarios involving changes in service relationships and analyze the 14 Top-1 regressions caused by knowledge updates? This would help substantiate the claimed continual self-improvement capability.