SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2402.01140 · AAAI · 2024

Root Cause Analysis in Microservice Using Neural Granger Causal Discovery

Ching Chang, Wen-Chih Peng, Kuang-Da Wang, Wei-Yao Wang, Cheng-Ming Lin

arXiv · PDF · Open in the Atlas

Code that ran

4 of 5 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (1 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 1 has no contract verdict; 3 failures of our instrument; 1 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2402.01140.json · badge: /api/ran/2402.01140.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
zmlin1998/run canonical (classifier label)
classifier basis: census
3 ran · 1 no recorded run
zmlin1998/RUN community
Papers with Code archive
1 ran · 0 no recorded run
FunctionStatusWhere it lives
DLinear Ran
ran on a synthesized input · constructed an object; no result was computed
zmlin1998/RUN/model.py
pointer only (licence: NONE) · get_code("d542323e0b8dd17d")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, zmlin1998/RUN when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

hierarchical_contrastive_loss Ran
ran; our contract draft was wrong, not the code
zmlin1998/run/models/losses.py
pointer only (licence: NONE) · get_code("8437171ce7bbbb51")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, zmlin1998/run when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

pearson_correlation Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
zmlin1998/run/models/utils.py
pointer only (licence: NONE) · get_code("a2bb0bd2911a8eca")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, zmlin1998/run when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

temporal_contrastive_loss Ran
ran; our contract draft was wrong, not the code
zmlin1998/run/models/losses.py
pointer only (licence: NONE) · get_code("7b689be4ab7220b3")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, zmlin1998/run when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

breaktie Not yet run
unverified (harvested, no recorded run)
zmlin1998/run/models/utils.py
pointer only (licence: NONE) · get_code("7c60f7bf1986601a")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, zmlin1998/run when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. No invocation recorded.

Also present in other papers' code

Of 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 5 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

In recent years, microservices have gained widespread adoption in IT operations due to their scalability, maintenance, and flexibility. However, it becomes challenging for site reliability engineers (SREs) to pinpoint the root cause due to the complex relationships in microservices when facing system malfunctions. Previous research employed structured learning methods (e.g., PC-algorithm) to establish causal relationships and derive root causes from causal graphs. Nevertheless, they ignored the temporal order of time series data and failed to leverage the rich information inherent in the temporal relationships. For instance, in cases where there is a sudden spike in CPU utilization, it can lead to an increase in latency for other microservices. However, in this scenario, the anomaly in CPU utilization occurs before the latency increase, rather than simultaneously. As a result, the PC-algorithm fails to capture such characteristics. To address these challenges, we propose RUN, a novel approach for root cause analysis using neural Granger causal discovery with contrastive learning. RUN enhances the backbone encoder by integrating contextual information from time series, and leverages a time series forecasting model to conduct neural Granger causal discovery. In addition, RUN incorporates Pagerank with a personalization vector to efficiently recommend the top-k root causes. Extensive experiments conducted on the synthetic and realworld microservice-based datasets demonstrate that RUN noticeably outperforms the state-of-the-art root cause analysis methods. Moreover, we provide an analysis scenario for the sock-shop case to showcase the practicality and efficacy of RUN in microservice-based applications. Our code is publicly available at https://github.com/zmlin1998/RUN.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2402.01140")
get_code_for_paper("2402.01140")
have("2402.01140")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2402.01140.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2402.01140.svg)](https://syntology.ai/paper/2402.01140)

Connect an agent — have() is free.