Automatic Failure Diagnosis Support in Distributed Large-Scale Software Systems Based on Timing Behavior Anomaly Correlation
The DOI matches its Crossref record.
Abstract
Manual failure diagnosis in large-scale software systems is time-consuming and error-prone. Automatic failure diagnosis support mechanisms can potentially narrow down, or even localize faults within a very short time which both helps to preserve system availability. A large class of automatic failure diagnosis approaches consists of two steps: 1) computation of component anomaly scores; 2) global correlation of the anomaly scores for fault localization. In this paper, we present an architecture-centric approach for the second step. In our approach, component anomaly scores are correlated based on architectural dependency graphs of the software system and a rule set to address error propagation. Moreover, the results are graphically visualized in order to support fault localization and to enhance maintainability. The visualization combines architectural diagrams automatically derived from monitoring data with failure diagnosis results. In a case study, the approach is applied to a distributed sample Web application which is subject to fault injection.
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
Cited by
CloudRanger: Root Cause Identification for Cloud Native Systems
Wang, P., Xu, J., Ma, M., Lin, W., Pan, D., Wang, Y., & Chen, P. (2018) · 2018 18th IEEE/ACM International Symposium on Cluster, Cloud and Grid Computing (CCGRID) · doi:10.1109/ccgrid.2018.00076 · Cited by 181
“Threekinds of methods are selected for comparison, namely random selection, TBAC [29] (Timing Behavior Anomaly Correlation) and MonitorRank [14].”
MethodEadro: An End-to-End Troubleshooting Framework for Microservices on Multi-source Data
Lee, C., Yang, T., Chen, Z., Su, Y., & Lyu, M. R. (2023) · 2023 IEEE/ACM 45th International Conference on Software Engineering (ICSE) · doi:10.1109/icse48619.2023.00150 · Cited by 149
“For root cause localization, we compare Eadro with five trace-based baselines: TBAC [10], NetMedic [52], MonitorRank [8], CloudRanger [11], and DyCause [6].”
Root cause detection in a service-oriented architecture
Kim, M., Sumbaly, R., & Shah, S. (2013) · ACM SIGMETRICS Performance Evaluation Review · doi:10.1145/2494232.2465753 · Cited by 138
AutoMAP: Diagnose Your Microservice-based Web Applications Automatically
Ma, M., Xu, J., Wang, Y., Chen, P., Zhang, Z., & Wang, P. (2020) · Proceedings of The Web Conference 2020 · doi:10.1145/3366423.3380111 · Cited by 129
“Also, compared to static algorithms (TBAC, NetMedic, MonitorRank, CloudRanger), random walk scheme can identify the root cause with higher accuracy.”
MethodInfluentialQiu, J., Du, Q., Yin, K., Zhang, S.-L., & Qian, C. (2020) · Applied Sciences · doi:10.3390/app10062166 · Cited by 96
“Many research papers on RCA focus on complex large-scale systems [1–4]; they can be grouped into the following categories: Event correlation analysis-based methods .”
Background
Metadata
- Authors
- Marwede, N., Rohr, M., van Hoorn, A., & Hasselbring, W.
- Venue
- 2009 13th European Conference on Software Maintenance and Reengineering
- Publisher
- IEEE
- Published
- 2009-03
- Pages
- 47-58
- ISSN
- 1534-5351 (ISSN-L)
- OpenAlex
- W2104050994
- Cited by
- 63
- References
- 0
- FWCI
- 2.97
- 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: Automatic Failure Diagnosis Support in Distributed Large-Scale Software Systems Based on Timing Behavior Anomaly Correlation. https://app.cochat.ai/papers/10.1109/csmr.2009.15
- The paper
- Marwede, N., Rohr, M., van Hoorn, A., & Hasselbring, W. (2009). Automatic Failure Diagnosis Support in Distributed Large-Scale Software Systems Based on Timing Behavior Anomaly Correlation. 2009 13th European Conference on Software Maintenance and Reengineering. https://doi.org/10.1109/csmr.2009.15
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.