?-Diagnosis: Unsupervised and Real-time Diagnosis of Small- window Long-tail Latency in Large-scale Microservice Platforms
Open accessThe DOI matches its Crossref record; 4 of the 4 references it cites were found in a registry or an index.
Abstract
Microservice architectures and container technologies are broadly adopted by giant internet companies to support their web services, which typically have a strict service-level objective (SLO), tail latency, rather than average latency. However, diagnosing SLO violations, e.g., long tail latency problem, is non-trivial for large-scale web applications in shared microservice platforms due to million-level operational data and complex operational environments.
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
(2007) · doi:10.1145/1294261.1294281 · Cited by 3,447 · cited 1×
“Tail latency [3, 7–9, 18, 19, 22, 25, 29, 29, 38, 44, 48, 49] becomes the main consideration as Service Level Objective (SLO) on performance [1, 30] for today’s most of systems and applications, such as search engine [7, 25], key-value store [9, 21], datacenter network system [22, 48], shared networked storage [49], o…”
Dean, J., & Barroso, L. A. (2013) · Communications of the ACM · doi:10.1145/2408776.2408794 · Cited by 1,852 · cited 1×
“Tail latency [3, 7–9, 18, 19, 22, 25, 29, 29, 38, 44, 48, 49] becomes the main consideration as Service Level Objective (SLO) on performance [1, 30] for today’s most of systems and applications, such as search engine [7, 25], key-value store [9, 21], datacenter network system [22, 48], shared networked storage [49], o…”
(2015) · doi:10.1145/2815400.2815415 · Cited by 202 · cited 1×
“Traditional rule (or signature) based performance diagnosis approaches for distributed systems, heavily depend on the operational fault knowledge base (such as Fingerprint [2, 6, 11]), and detect the anomaly and performance bottlenecks through tracing the request process flowing in large-scale distributed system (such…”
Survey on Models and Techniques for Root-Cause Analysis
Solé, M., Muntés-Mulero, V., Rana, A. I., & Estrada, G. (2017) · arXiv · doi:10.48550/arxiv.1701.08546 · Cited by 74
Cited by
Soldani, J., & Brogi, A. (2023) · ACM Computing Surveys · doi:10.1145/3501297 · Cited by 256
“𝜖 -diagnosis -diagnosis [77] however focuses on the tail latency of the application frontend, determined in small time windows (e.g., one minute or one second), rather than on bigger ones as typically done.”
BackgroundMethodInfluentialRoot-Cause Metric Location for Microservice Systems via Log Anomaly Detection
Wang, L., Zhao, N., Chen, J., Li, P., Zhang, W., & Sui, K. (2020) · 2020 IEEE International Conference on Web Services (ICWS) · doi:10.1109/icws49710.2020.00026 · Cited by 84
Failure Diagnosis in Microservice Systems: A Comprehensive Survey and Analysis
Zhang, S., Xia, S., Fan, W., Shi, B., Xiong, X., Zhong, Z., Ma, M., Sun, Y., & Pei, D. (2026) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3715005 · Cited by 57
ServiceRank: Root Cause Identification of Anomaly in Large-Scale Microservice Architectures
Ma, M., Lin, W., Pan, D., & Wang, P. (2022) · IEEE Transactions on Dependable and Secure Computing · doi:10.1109/tdsc.2021.3083671 · Cited by 46
Yu, G., Huang, Z., & Chen, P. (2023) · Journal of Software: Evolution and Process · doi:10.1002/smr.2413 · Cited by 44
Root Cause Analysis in Microservice Using Neural Granger Causal Discovery
Lin, C.-M., Chang, C., Wang, W.-Y., Wang, K.-D., & Peng, W.-C. (2024) · Proceedings of the AAAI Conference on Artificial Intelligence · doi:10.1609/aaai.v38i1.27772 · Cited by 39
Root Cause Analysis for Microservice System based on Causal Inference: How Far Are We?
Pham, L., Ha, H., & Zhang, H. (2024) · Proceedings of the 39th IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/3691620.3695065 · Cited by 38
Huang, L., & Zhu, T. (2021) · Proceedings of the ACM Symposium on Cloud Computing · doi:10.1145/3472883.3486994 · Cited by 37
Anomaly Detection in Microservice-Based Systems
Nobre, J., Pires, E. J. S., & Reis, A. (2023) · Applied Sciences · doi:10.3390/app13137891 · Cited by 34
HeMiRCA: fine-grained root cause analysis for microservices with heterogeneous data sources
Zhu, Z., Lee, C., Tang, X., & He, P. (2024) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3674726 · Cited by 26
“Some approaches rely on traces [25, 26, 33, 41] because traces record essential inter-service information (e.g., request duration), while others rely on metrics [11, 32, 39, 40, 43, 45] since metrics reflect diverse aspects of the system status (e.g., CPU usages, network).”
BackgroundInfluentialAI for IT Operations (AIOps) on Cloud Platforms: Reviews, Opportunities and Challenges
Cheng, Q., Sahoo, D., Saha, A., Yang, W., Liu, C., Woo, G., Singh, M., Saverese, S., & Hoi, S. C. H. (2023) · arXiv · doi:10.48550/arxiv.2304.04661 · Cited by 23
MRCA: metric-level root cause analysis for microservices via multi-modal data
Wang, Y., Zhu, Z., Fu, Q., Ma, Y., & He, P. (2024) · Proceedings of the 39th IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/3691620.3695485 · Cited by 18
“For instance, the 𝜖 -Diagnosis [36] uses 𝜖 -statistics to identify key metrics causing small-window long-tail latency in web services.”
ModelCoder: A Fault Model based Automatic Root Cause Localization Framework for Microservice Systems
Cai, Y., Han, B., Li, J., Zhao, N., & Su, J. (2021) · 2021 IEEE/ACM 29th International Symposium on Quality of Service (IWQOS) · doi:10.1109/iwqos52092.2021.9521318 · Cited by 14
PyRCA: A Library for Metric-based Root Cause Analysis
Liu, C., Yang, W., Mittal, H., Singh, M., Sahoo, D., & Hoi, S. C. H. (2023) · arXiv · doi:10.48550/arxiv.2306.11417 · Cited by 4
Anomaly detection and root-cause identification in microservices: a survey
Barata, L. M., Sequeira, S., Lopes, E., Inácio, P. R. M., & Freire, M. M. (2026) · Cluster Computing · doi:10.1007/s10586-026-06095-9 · Cited by 4
Metadata
- Authors
- Shan, H., Chen, Y., Liu, H., Zhang, Y., Xiao, X., He, X., Li, M., & Ding, W.
- Venue
- The World Wide Web Conference
- Publisher
- ACM
- Published
- 2019-05-13
- Pages
- 3215-3222
- OpenAlex
- W2913603385
- Cited by
- 73
- References
- 4
- FWCI
- 3.78
- Type
- conference paper
- Language
- en
- Open access
- gold
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
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.