Root cause detection in a service-oriented architecture
The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Abstract
Large-scale websites are predominantly built as a service-oriented architecture. Here, services are specialized for a certain task, run on multiple machines, and communicate with each other to serve a user's request. An anomalous change in a metric of one service can propagate to other services during this communication, resulting in overall degradation of the request. As any such degradation is revenue impacting, maintaining correct functionality is of paramount concern: it is important to find the root cause of any anomaly as quickly as possible. This is challenging because there are numerous metrics or sensors for a given service, and a modern website is usually composed of hundreds of services running on thousands of machines in multiple data centers.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Chandola, V., Banerjee, A., & Kumar, V. (2009) · ACM Computing Surveys · doi:10.1145/1541880.1541882 · Cited by 11,687 · cited 1×
“We restrict our focus to diagnosis after an anomaly has been reported, thereby distinguishing our work from the anomaly detection literature [3, 5, 26].”
MethodEfron, B., Hastie, T., Johnstone, I., & Tibshirani, R. (2004) · The Annals of Statistics · doi:10.1214/009053604000000067 · Cited by 9,357
Detection of Abrupt Changes: Theory and Application
Riedel, K. S. (1994) · Technometrics · doi:10.1080/00401706.1994.10485821 · Cited by 3,518
Scaling personalized web search
Jeh, G., & Widom, J. (2003) · Proceedings of the twelfth international conference on World Wide Web - WWW '03 · doi:10.1145/775152.775191 · Cited by 1,195 · cited 1×
“Therefore, MonitorRank uses the Personalized PageRank algorithm [14], by taking teleportation probability (preference vector) as determined by the given anomaly.”
MethodA survey of fault localization techniques in computer networks
Steinder, M. Ł., & Sethi, A. S. (2004) · Science of Computer Programming · doi:10.1016/j.scico.2004.01.010 · Cited by 358
Cited by
Gleich, D. F. (2015) · SIAM Review · doi:10.1137/140976649 · Cited by 646
Soldani, J., & Brogi, A. (2023) · ACM Computing Surveys · doi:10.1145/3501297 · Cited by 256
“The candidate services are scored by visiting the causality graph with the random walk-based algorithm proposed by MonitorRank [38] (which we present in Section 4.2.3).”
BackgroundMethodInfluentialMicroRCA: Root Cause Localization of Performance Issues in Microservices
Wu, L., Tordsson, J., Elmroth, E., & Kao, O. (2020) · NOMS 2020 - 2020 IEEE/IFIP Network Operations and Management Symposium · doi:10.1109/noms47738.2020.9110353 · Cited by 265
(2015) · doi:10.1145/2815400.2815415 · Cited by 202
MicroHECL: High-Efficient Root Cause Localization in Large-Scale Microservice Systems
Liu, D., He, C., Peng, X., Lin, F., Zhang, C., Gong, S., Li, Z., Ou, J., & Wu, Z. (2021) · 2021 IEEE/ACM 43rd International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1109/icse-seip52600.2021.00043 · Cited by 192
“• MonitorRank [6]: It detects root causes of anomalies in service-oriented systems and provides a ranked order list of possible root causes.”
BackgroundMethodInfluential
Metadata
- Authors
- Kim, M., Sumbaly, R., & Shah, S.
- Venue
- Proceedings of the ACM SIGMETRICS/international conference on Measurement and modeling of computer systems
- Publisher
- ACM
- Published
- 2013-06-17
- Pages
- 93-104
- OpenAlex
- W2049298676
- Cited by
- 73
- References
- 5
- FWCI
- 3.33
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Root cause detection in a service-oriented architecture. https://app.cochat.ai/papers/10.1145/2465529.2465753
- The paper
- Kim, M., Sumbaly, R., & Shah, S. (2013). Root cause detection in a service-oriented architecture. Proceedings of the ACM SIGMETRICS/international conference on Measurement and modeling of computer systems. https://doi.org/10.1145/2465529.2465753
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.