Event Logs for the Analysis of Software Failures: A Rule-Based Approach
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Event logs have been widely used over the last three decades to analyze the failure behavior of a variety of systems. Nevertheless, the implementation of the logging mechanism lacks a systematic approach and collected logs are often inaccurate at reporting software failures: This is a threat to the validity of log-based failure analysis. This paper analyzes the limitations of current logging mechanisms and proposes a rule-based approach to make logs effective to analyze software failures. The approach leverages artifacts produced at system design time and puts forth a set of rules to formalize the placement of the logging instructions within the source code. The validity of the approach, with respect to traditional logging mechanisms, is shown by means of around 12,500 software fault injection experiments into real-world systems.
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
Detecting large-scale system problems by mining console logs
Xu, W., Huang, L., Fox, A., Patterson, D., & Jordan, M. I. (2009) · Proceedings of the ACM SIGOPS 22nd symposium on Operating systems principles · doi:10.1145/1629575.1629587 · Cited by 1,332 · cited 1×
“Despite a number of works proposing log filtering and coalescence algorithms [15], [16], [17], [9], [4], [18], [10], the real problem with failure analysis is the scarce ability of current logs at reporting the right set of error events, i.e., the ones leading to failures.”
Background
Research works printed but not linked: 49
- 10.2514/1.49356 · doi:10.2514/1.49356
- Bauer, Runtime Reflection: Dynamic Model-Based Analysis of Component-Based Distributed Embedded Systems
- 10.1007/978-0-387-72258-0_29 · doi:10.1007/978-0-387-72258-0_29
- 10.1109/DSN.2007.103 · DOI · Paper page
- 10.1007/3-540-46506-5_7 · doi:10.1007/3-540-46506-5_7
- 10.1109/RELDIS.1999.805094 · doi:10.1109/reldis.1999.805094
- 10.1109/PRDC.2005.20 · doi:10.1109/prdc.2005.20
- 10.1109/DSN.2006.18 · DOI · Paper page
- 10.1109/DSN.2011.5958210 · DOI
- Oppenheimer, Why Do Internet Services Fail, and What Can Be Done about It?”
- 10.1109/DSN.2006.5 · DOI · Paper page
- 10.1109/TDSC.2004.2 · DOI · Paper page
- 10.1109/FTCS.1995.466958 · doi:10.1109/ftcs.1995.466958
- 10.1109/FTCS.1992.243597 · DOI
- 10.1109/ISSRE.2001.989489 · doi:10.1109/issre.2001.989489
- 10.1145/956750.956799 · DOI · Paper page
- 10.1109/TDSC.2004.20 · DOI
- 10.1109/ICDCS.2006.37 · doi:10.1109/icdcs.2006.37
- 10.1109/PRDC.1999.816227 · doi:10.1109/prdc.1999.816227
- 10.1109/DSN.2010.5544279 · DOI
- 10.17487/rfc3164 · doi:10.17487/rfc3164
- Murray, Windows NT Event Logging
- 10.1109/24.756088 · doi:10.1109/24.756088
- 10.1109/24.556579 · DOI
- 10.1109/IPOM.2002.1045765 · doi:10.1109/ipom.2002.1045765
- Rouillard, Real-Time Log File Analysis Using the Simple Event Correlator (SEC)
- Iyer, Recognition of Error Symptoms in Large Systems, 797
- 10.1109/FTCS.1996.534614 · doi:10.1109/ftcs.1996.534614
- 10.1109/NCA.2008.57 · doi:10.1109/nca.2008.57
- 2012, Apache log4j
- 10.1145/383845.383853 · doi:10.1145/383845.383853
- 10.1109/52.895163 · doi:10.1109/52.895163
- 10.1109/IPDPS.2004.1303243 · DOI
- 10.1145/1950365.1950369 · DOI · Paper page
- Rabkin, A Graphical Representation for Identifier Structure in Logs
- 10.1109/DSN.2002.1029005 · DOI · Paper page
- David, Exploring Recovery from Operating System Lockups, 1
- 10.1109/TR.2007.909758 · doi:10.1109/tr.2007.909758
- 10.1145/356678.356681 · DOI
- 10.1109/ICDSN.2000.857510 · doi:10.1109/icdsn.2000.857510
- Cantrill, Dynamic Instrumentation of Production Systems
- Tamches, Fine-Grained Dynamic Instrumentation of Commodity Operating System Kernels
- 2012, SLOCCount
- Stallings, 2008, Operating Systems, Internals and Design Principles
- 10.1109/TSE.2006.113 · DOI · Paper page
- 10.1109/TSE.2011.124 · DOI · Paper page
- 10.1109/DSN.2008.4630109 · DOI · Paper page
- 10.1109/CCGRID.2008.107 · DOI
- 10.1145/1851275.1851192 · DOI · Paper page
Cited by
DeepLog: Anomaly Detection and Diagnosis from System Logs through Deep Learning
Du, M., Li, F., Zheng, G., & Srikumar, V. (2017) · Proceedings of the 2017 ACM SIGSAC Conference on Computer and Communications Security · doi:10.1145/3133956.3134015 · Cited by 1,835
LogBERT: Log Anomaly Detection via BERT
Guo, H., Yuan, S., & Wu, X. (2021) · 2021 International Joint Conference on Neural Networks (IJCNN) · doi:10.1109/ijcnn52387.2021.9534113 · Cited by 454
“To tackle this challenge, many rule-based approaches are proposed to identify anomalous events [11,20].”
BackgroundA Survey on Automated Log Analysis for Reliability Engineering
He, S., He, P., Chen, Z., Yang, T., Su, Y., & Lyu, M. R. (2022) · ACM Computing Surveys · doi:10.1145/3460345 · Cited by 334
MLog: Mogrifier LSTM-Based Log Anomaly Detection Approach Using Semantic Representation
Fu, Y., Liang, K., & Xu, J. (2023) · IEEE Transactions on Services Computing · doi:10.1109/tsc.2023.3289488 · Cited by 49
LogBERT: Log Anomaly Detection via BERT
Guo, H., Yuan, S., & Wu, X. (2021) · arXiv · doi:10.48550/arxiv.2103.04475 · Cited by 7
Metadata
- Authors
- Cinque, M., Cotroneo, D., & Pecchia, A.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2013-06
- Volume
- 39
- Issue
- 6
- Pages
- 806-821
- ISSN
- 0098-5589 (ISSN-L)
- 1939-3520
- OpenAlex
- W2096017373
- Cited by
- 125
- References
- 1
- FWCI
- 6.33
- Type
- journal article
- 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
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.