Anomaly Detection and Failure Root Cause Analysis in (Micro) Service-Based Cloud Applications: A Survey
Open accessThe DOI matches its Crossref record; 104 of the 104 references it cites were found in a registry or an index.
Abstract
The proliferation of services and service interactions within microservices and cloud-native applications, makes it harder to detect failures and to identify their possible root causes, which is, on the other hand crucial to promptly recover and fix applications. Various techniques have been proposed to promptly detect failures based on their symptoms, viz., observing anomalous behaviour in one or more application services, as well as to analyse logs or monitored performance of such services to determine the possible root causes for observed anomalies. The objective of this survey is to provide a structured overview and qualitative analysis of currently available techniques for anomaly detection and root cause analysis in modern multi-service applications. Some open challenges and research directions stemming out from the analysis are also discussed.
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.
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
The cited source says what the claim attributes to it.
In the citing paper
“Only two survey publications [26,27] directly related to our work were found in the most relevant digital libraries (IEEE Xplore, ACM Digital Library, Science Direct, Wiley Online Library, Springer Link, Scopus, and Web of Science).”
From Anomaly detection and root-cause identification in microservices: a survey (2026) · cites this paper as [26]
The cited source says what the claim attributes to it.
In the citing paper
“Soldani and Brogi [26] focused on microservices architecture.”
From Anomaly detection and root-cause identification in microservices: a survey (2026) · cites this paper as [26]
The cited source says what the claim attributes to it.
In the citing paper
“System faults observed in microservice applications include, but are not limited to, network latency, anomalous resource consumption and unavailability of system components [5].”
From Toward Context-Aware Anomaly Detection for AIOps in Microservices Using Dynamic Knowledge Graphs (2026) · cites this paper as [5]
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
Breiman, L. (2001) · Machine Learning · doi:10.1023/a:1010933404324 · Cited by 133,538 · cited 3×
“…runs of the application, in such a way that it can be processed to train a classifier with a supervised machine learning algorithm (viz., nearest neighbour [3], random forest [10], naïve Bayes [36], or support vector machines [76]), assuming that no more than one anomaly occurs at the same time.”
BackgroundMethodAdam: A Method for Stochastic Optimization
Kingma, D. P., & Ba, J. (2014) · arXiv · doi:10.48550/arxiv.1412.6980 · Cited by 98,946 · cited 1×
“, a variational autoencoder [39] modelling the normal behaviour of the application and a convolutional neural network [23] recognising the type of failure affecting a service when the latter is affected by a performance anomaly.”
BackgroundJolliffe, I. (2005) · Encyclopedia of Statistics in Behavioral Science · doi:10.1002/0470013192.bsa501 · Cited by 14,310
Chandola, V., Banerjee, A., & Kumar, V. (2009) · ACM Computing Surveys · doi:10.1145/1541880.1541882 · Cited by 11,687 · cited 5×
“This is checked by applying formerly trained machine learning models for offline detection of anomalies on each service, viz., support vector machines [76] for latency anomalies, random forests [10] for error count anomalies, and 3-sigma rule [16] for throughput anomalies.”
BackgroundMethodInfluentialPeng, H., Long, F., & Ding, C. (2005) · IEEE Transactions on Pattern Analysis and Machine Intelligence · doi:10.1109/tpami.2005.159 · Cited by 10,544 · cited 1×
“Wang et al. [86] then apply mutual information [64] to determine the dependency of the anomaly degree on the KPIs monitored on application services in the same interval.”
BackgroundRobust principal component analysis?
Candès, E. J., Li, X., Ma, Y., & Wright, J. (2011) · Journal of the ACM · doi:10.1145/1970392.1970395 · Cited by 6,921 · cited 1×
“When a matrix is corrupted by gross sparse errors, RPCA can extract the columns where the errors appear [13].”
Advances in kernel methods: support vector learning
Schölkopf, B., Burges, C. J. C., & Smola, A. J. (1999) · doi:10.5555/299094 · Cited by 5,789 · cited 2×
“…runs of the application, in such a way that it can be processed to train a classifier with a supervised machine learning algorithm (viz., nearest neighbour [3], random forest [10], naïve Bayes [36], or support vector machines [76]), assuming that no more than one anomaly occurs at the same time.”
BackgroundMethodAn Introduction to Kernel and Nearest-Neighbor Nonparametric Regression
Altman, N. S. (1992) · The American Statistician · doi:10.1080/00031305.1992.10475879 · Cited by 5,708 · cited 2×
“, nearest neighbour [3], random forest [10], naïve Bayes [36], or support vector machines [75]), assuming that no more than one anomaly occurs at the same time.”
BackgroundHandbook of Parametric and Nonparametric Statistical Procedures
(2004) · Technometrics · doi:10.1198/tech.2004.s209 · Cited by 4,661
Causation, Prediction, and Search
Spirtes, P., Glymour, C., & Scheines, R. (2001) · doi:10.7551/mitpress/1754.001.0001 · Cited by 4,521
Research works printed but not linked: 17
- 10.5555/151741 · doi:10.5555/151741
- 10.5555/1965046 · doi:10.5555/1965046
- 10.5555/3086952 · doi:10.5555/3086952
- 10.5555/1869904 · doi:10.5555/1869904
- IBM. 2021. IBM operations analytics predictive insights. Retrieved November 18th, 2021 from https://www.ibm.com/support/knowledgecenter/SSJQQ3.
- Istio Authors. 2020. Istio. Retrieved November 18th, 2021 from https://istio.io.
- 10.5555/2074158.2074196 · doi:10.5555/2074158.2074196
- J. Lewis and M. Fowler. 2014. Microservices. ThoughtWorks. Retrieved from https://martinfowler.com/articles/microservices.html.
- 10.5555/541177 · doi:10.5555/541177
- 10.5555/525544 · doi:10.5555/525544
- Prometheus Authors. 2021. Prometheus: Monitoring System & Time Series Database. Retrieved November 18th, 2021 from https://prometheus.io.
- 10.5555/3045118.3045281 · doi:10.5555/3045118.3045281
- C. Richardson. 2018. Microservices Patterns (1st ed.). Manning Publications, Shelter Island.
- 10.5555/1594884 · doi:10.5555/1594884
- 10.5555/1529939 · doi:10.5555/1529939
- 10.5555/1088844 · doi:10.5555/1088844
- A. van Hoorn. 2014. Model-Driven Online Capacity Management for Component-Based Software Systems. Ph.D. Dissertation. Faculty of Engineering Kiel University Kiel Germany.
Cited by
Practical autoencoder based anomaly detection by using vector reconstruction error
Torabi, H., Mirtaheri, S. L., & Greco, S. (2023) · Cybersecurity · doi:10.1186/s42400-022-00134-9 · Cited by 168
“Many approaches and methods for security monitoring in cloud computing networks have been introduced [11].”
Xin, R., Chen, P., & Zhao, Z. (2023) · Journal of Systems and Software · doi:10.1016/j.jss.2023.111724 · Cited by 99
“To track the root cause localization problem of microservice applications, some research has been provided in recent years [2].”
BackgroundMethodInfluentialA Survey of Graph-Based Deep Learning for Anomaly Detection in Distributed Systems
Pazho, A. D., Noghre, G. A., Purkayastha, A. A., Vempati, J., Martin, O., & Tabkhi, H. (2023) · IEEE Transactions on Knowledge and Data Engineering · doi:10.1109/tkde.2023.3282898 · Cited by 145
“One of the major differences between GSP and traditional Machine learning algorithms is that ML typically considers a graph as a discrete version of a complex network.”
BackgroundAutomation and Orchestration of Zero Trust Architecture: Potential Solutions and Challenges
Cao, Y., Pokhrel, S. R., Zhu, Y., Doss, R., & Li, G. (2024) · Machine Intelligence Research · doi:10.1007/s11633-023-1456-2 · Cited by 97
MULAN: Multi-modal Causal Structure Learning and Root Cause Analysis for Microservice Systems
Zheng, L., Chen, Z., He, J., & Chen, H. (2024) · International World Wide Web Conference (WWW) · doi:10.1145/3589334.3645442 · Cited by 127
“Numerous domain-specific RCA approaches [11, 23, 26, 33–35 , 46] have been developed to enhance the resilience of applications.”
BackgroundMethod
Metadata
- Authors
- Soldani, J., & Brogi, A.
- Affiliations
- University of Pisa (IT)
- University of Pisa, Pisa, PI, Italy
- Venue
- ACM Computing Surveys
- Published
- 2022-02-03
- Volume
- 55
- Issue
- 3
- Pages
- 1-39
- ISSN
- 0360-0300 (ISSN-L)
- 1557-7341
- OpenAlex
- W3165186175
- Cited by
- 256
- References
- 95
- Citations by year
- 2026: 78 · 2025: 63 · 2024: 67 · 2023: 31 · 2022: 15
- FWCI
- 19.53
- Type
- journal article
- Language
- en
- Open access
- green
- arxiv.org
- Locations
- ACM Computing Surveys (publishedVersion)
- arXiv (Cornell University) (submittedVersion)
- CINECA IRIS Institutial research information system (University of Pisa) (submittedVersion, other-oa)
- arXiv (Cornell University)
- Topics
- Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
- Physical Sciences › Computer Science › Information Systems › Cloud Computing and Resource Management
- Physical Sciences › Computer Science › Computer Networks and Communications › Distributed systems and fault tolerance
- Keywords
- anomaly detection, root cause analysis, microservices, cloud-native applications, log analysis, performance monitoring, fault diagnosis, service failure
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: Anomaly Detection and Failure Root Cause Analysis in (Micro) Service-Based Cloud Applications: A Survey. https://app.cochat.ai/papers/10.1145/3501297
- The paper
- Soldani, J., & Brogi, A. (2023). Anomaly Detection and Failure Root Cause Analysis in (Micro) Service-Based Cloud Applications: A Survey. ACM Computing Surveys. https://doi.org/10.1145/3501297
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.