MétaCan
Menu
Back to cohort

Identifying Failure Root Causes for Cloud-Native Microservice Applications

2025· article· W4416184140 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Language
FieldComputer Science
TopicSoftware System Performance and Reliability
Canadian institutionsIBM (Canada)York University
Fundersnot available
KeywordsRoot cause analysisRoot causeRoot (linguistics)DebuggingObservabilityPreprocessorMetric (unit)Redundancy (engineering)

Abstract

fetched live from OpenAlex

Cloud-native microservice applications depend on reliable platforms to ensure stable performance, even under resource overload faults. However, understanding the root causes of system failures holistically remains a significant challenge. This paper proposes a novel, root cause-oriented framework that supports autonomic, self-managing systems with humans in the loop. Our approach leverages a three-fold modality of observability data—logs, metrics, and traces—to build a multi-perspective view of system behavior. We enhance preprocessing to extract metric anomaly scores and log semantics (e.g., Template ID counts and Golden Signal counts), which are then fused to train a GNN-GRU model. This model captures spatial and temporal patterns across services to classify failure types and identify the root causes behind them. The resulting root cause predictions—including correlated anomalies and their associated source and target services—are analyzed to provide context-rich insights, aiding human operators (e.g., SREs) in debugging and diagnosis. Our framework fits naturally into the Monitor-Analyze-Plan-Execute (MAPE) loop, enabling proactive fault management and feedback-driven improvement. Evaluations using the public MicroSS dataset—comprising faults like resource saturation and configuration errors—demonstrate the effectiveness of our method in accurately identifying failure origins and supporting operational resilience.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.931
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0010.000
Scholarly communication0.0010.001
Open science0.0020.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.018
GPT teacher head0.305
Teacher spread0.287 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it