The DOI matches its Crossref record; 51 of the 51 references it cites were found in a registry or an index.
TrinityRCL: Multi-Granular and Code-Level Root Cause Localization Using Multiple Types of Telemetry Data in Microservice Systems
Abstract
The microservice architecture has been commonly adopted by large scale software systems exemplified by a wide range of online services. Service monitoring through anomaly detection and root cause analysis (RCA) is crucial for these microservice systems to provide stable and continued services. However, compared with monolithic systems, software systems based on the layered microservice architecture are inherently complex and commonly involve entities at different levels of granularity. Therefore, for effective service monitoring, these systems have a special requirement of multi-granular RCA. Furthermore, as a large proportion of anomalies in microservice systems pertain to problematic code, to timely troubleshoot these anomalies, these systems have another special requirement of RCA at the finest code-level. Microservice systems rely on telemetry data to perform service monitoring and RCA of service anomalies. The majority of existing RCA approaches are only based on a single type of telemetry data and as a result can only support uni-granular RCA at either application-level or service-level. Although there are attempts to combine metric and tracing data in RCA, their objective is to improve RCA's efficiency or accuracy rather than to support multi-granular RCA. In this article, we propose a new RCA solutionTrinityRCLthat is able to localize the root causes of anomalies at multiple levels of granularity including application-level, service-level, host-level, and metric-level, with the unique capability of code-level localization by harnessing all three types of telemetry data to construct a causal graph representing the intricate, dynamic, and nondeterministic relationships among the various entities related to the anomalies. By implementing and deployingTrinityRCLin a real production environment, we evaluateTrinityRCLagainst two baseline methods and the results show thatTrinityRCLhas a significant performance advantage in terms of accuracy at the same level of granularity with comparable efficiency and is particularly effective to support large-scale systems with massive telemetry data.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
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?
In the citing paper
“The worth of the collected information is a primary factor; therefore, combining sources can enhance data quality [131] by collecting performance indicators from logs or real-time monitoring, but also from traces, which is an important source of anomaly information in a microservices architecture.”
From Anomaly detection and root-cause identification in microservices: a survey (2026) · cites this paper as [131]
Citations
Cites
(1994) · Knowledge Discovery and Data Mining · Cited by 3,137
Pearson Correlation Coefficient
Benesty, J., Chen, J., Huang, Y., & Cohen, I. (2009) · Springer Topics in Signal Processing · doi:10.1007/978-3-642-00296-0_5 · Cited by 3,059
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 3×
“Kim et al. proposed an unsupervised algorithm Moni-torRank that used the historical and current time-series metrics along with the call graph to predict root causes of anomalies in service-oriented architectures by running the Personalized PageRank algorithm on the graph [18].”
MethodMicroservices Architecture Enables DevOps: Migration to a Cloud-Native Architecture
Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016) · IEEE Software · doi:10.1109/ms.2016.64 · Cited by 735 · cited 1×
“Furthermore, compared with the monolithic architecture, the microservices put new requirements on service monitoring and anomaly diagnosis [5].”
Microservices: The Journey So Far and Challenges Ahead
Jamshidi, P., Pahl, C., Mendonca, N. C., Lewis, J., & Tilkov, S. (2018) · IEEE Software · doi:10.1109/ms.2018.2141039 · Cited by 554 · cited 1×
“Most of these systems adopt the microservice architecture as it supports faster delivery, better resilience, and higher adaptability to dynamic customer requirements [1], [2].”
BackgroundObservability of complex systems
Liu, Y.-Y., Slotine, J.-J., & Barabási, A.-L. (2013) · Proceedings of the National Academy of Sciences · doi:10.1073/pnas.1215508110 · Cited by 516 · cited 1×
“Theoretically, by combining the aforementioned three typical types of telemetry data, we may be able to improve system observability [21] for better service monitoring, RCA and service quality assurance.”
BackgroundAutomatic multimedia cross-modal correlation discovery
Pan, J.-Y., Yang, H.-J., Faloutsos, C., & Duygulu, P. (2004) · Proceedings of the tenth ACM SIGKDD international conference on Knowledge discovery and data mining · doi:10.1145/1014052.1014135 · Cited by 479 · cited 1×
“To simulate the process of anomaly propagation, we localize root causes from the constructed causal graph with edges annotated byanomalyscoresvia RandomWalkwithRestart(RWR) [39]—a variant of Random Walk algorithm, which has been widely used for root cause localization [18], [19], [40].”
MethodZhou, X., Peng, X., Xie, T., Sun, J., Ji, C., Li, W., & Ding, D. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2018.2887384 · Cited by 410 · cited 1×
“Second, according to a recent industrial survey [7], most anomalies in a microservice system are caused by functional faults.”
BackgroundSeer: Leveraging Big Data to Navigate the Complexity of Performance Debugging in Cloud Microservices
Gan, Y., Zhang, Y., Hu, K., Cheng, D., He, Y., Pancholi, M., & Delimitrou, C. (2019) · Proceedings of the Twenty-Fourth International Conference on Architectural Support for Programming Languages and Operating Systems · doi:10.1145/3297858.3304004 · Cited by 269 · cited 1×
“Asmostmachinelearning-basedand rule-basedapproachesrelyheavilyonhistoricaldataformodel training[20],[32],[33],theconstantlychangingdatamay increasethenecessityforfrequentmodelupdatesandinevitably increasethecostofmodeltraining.”
MicroRCA: 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 · cited 24×
“presented a system that can infer root causes in real time by correlating application performance symptoms with corresponding system resource utilization metrics [2].”
BackgroundMethodInfluential
Research works printed but not linked: 3
- sridharan, 2018, Distributed Systems Observability A Guide to Building Robust Systems
- basili, 1994, Goal question metric paradigm, Encyclopaedia of Software Eng, 1, 528
- fowler, 2016, Production-Ready Microservices Building Standardized Systems Across an Engineering Organization
Cited by
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
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
“The idea is that the higher the correlation between the metrics monitored on an anomalous service and those monitored in parallel on other services, the higher the probability that the latter has caused the anomaly observed on the former.”
Xie, Z., Zhang, S., Geng, Y., Zhang, Y., Ma, M., Nie, X., Yao, Z., Xu, L., Sun, Y., Li, W., et al. (2024) · ACM SIGKDD Conference on Knowledge Discovery and Data Mining (KDD) · doi:10.1145/3637528.3671530 · Cited by 37
ART: A Unified Unsupervised Framework for Incident Management in Microservice Systems
Sun, Y., Shi, B., Mao, M., Ma, M., Xia, S., Zhang, S., & Pei, D. (2024) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3691620.3695495 · Cited by 71
“Thus, a large portion of automated incident management techniques primarily consists of anomaly detection (AD) [7, 22, 28, 36, 38, 41, 47, 55, 62, 63], failure triage (FT) [32, 35, 37, 48, 59, 61], and root cause localization (RCL) [6, 12, 16, 19, 34, 52, 57, 58, 64].”
Xie, S., Wang, J., He, H., Wang, Z., Zhao, Y., Zhang, N., & Li, B. (2025) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3734868 · Cited by 30
“Researchers have also shown interest in integrating the advantages of different modalities to further improve the performance of failure diagnosis [16, 19, 23, 44, 57, 66].”
Metadata
- Authors
- Gu, S., Rong, G., Ren, T., Zhang, H., Shen, H., Yu, Y., Li, X., Ouyang, J., & Chen, C.
- Affiliations
- Nanjing University (CN)
- Meituan (China) (CN)
- Australian Catholic University (AU)
- State Key Laboratory for Novel Software Technology, Nanjing University, Nanjing, Jiangsu, China
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2023-05-01
- Volume
- 49
- Issue
- 5
- Pages
- 3071-3088
- ISSN
- 0098-5589 (ISSN-L)
- 1939-3520
- 2326-3881
- OpenAlex
- W4318830451
- Cited by
- 46
- References
- 51
- Citations by year
- 2026: 22 · 2025: 14 · 2024: 9 · 2023: 1
- FWCI
- 5.12
- Type
- journal article
- Language
- en
- Open access
- closed
- Licence
- Locations
- IEEE Transactions on Software Engineering (publishedVersion)
- Funders
- National Key Research and Development Program of China (2019YFE0105500)
- Norges Forskningsråd (309494)
- Meituan
- Key Research and Development Program of Jiangsu Province (BE2021002-2)
- National Natural Science Foundation of China (62072227, 62202219)
- Topics
- Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Information Systems › Cloud Computing and Resource Management
- Keywords
- root cause localization, microservices, telemetry data, causal graphs, service monitoring
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: TrinityRCL: Multi-Granular and Code-Level Root Cause Localization Using Multiple Types of Telemetry Data in Microservice Systems. https://app.cochat.ai/papers/10.1109/tse.2023.3241299
- The paper
- Gu, S., Rong, G., Ren, T., Zhang, H., Shen, H., Yu, Y., Li, X., Ouyang, J., & Chen, C. (2023). TrinityRCL: Multi-Granular and Code-Level Root Cause Localization Using Multiple Types of Telemetry Data in Microservice Systems. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.2023.3241299
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.