Journal Article10.1007/S10664-016-9429-5
Characterizing logging practices in Java-based open source software projects --- a replication study in Apache Software Foundation
Boyuan Chen,Zhen Ming Jiang +1 more
129
TL;DR: A replication study of 21 different Java-based open source projects from three different categories shows that all projects contain logging code, which is actively maintained, however, contrary to the original study, bug reports containing log messages take a longer time to resolve than bug reports without log messages.
read more
Abstract: Log messages, which are generated by the debug statements that developers insert into the code at runtime, contain rich information about the runtime behavior of software systems. Log messages are used widely for system monitoring, problem diagnoses and legal compliances. Yuan et al. performed the first empirical study on the logging practices in open source software systems. They studied the development history of four C/C++ server-side projects and derived ten interesting findings. In this paper, we have performed a replication study in order to assess whether their findings would be applicable to Java projects in Apache Software Foundations. We examined 21 different Java-based open source projects from three different categories: server-side, client-side and supporting-component. Similar to the original study, our results show that all projects contain logging code, which is actively maintained. However, contrary to the original study, bug reports containing log messages take a longer time to resolve than bug reports without log messages. A significantly higher portion of log updates are for enhancing the quality of logs (e.g., formatting & style changes and spelling/grammar fixes) rather than co-changes with feature implementations (e.g., updating variable names).
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
The ABC of Software Engineering Research
Klaas-Jan Stol,Brian Fitzgerald +1 more
TL;DR: A taxonomy from the social sciences is adopted, termed here the ABC framework for SE research, which offers a holistic view of eight archetypal research strategies, and six ways in which the framework can advance SE research.
270
•Posted Content
A Survey on Automated Log Analysis for Reliability Engineering.
TL;DR: This survey presents a detailed overview of automated log analysis research, including how to automate and assist the writing of logging statements, how to compress logs,How to parse logs into structured event templates, and how to employ logs to detect anomalies, predict failures, and facilitate diagnosis.
Characterizing and detecting anti-patterns in the logging code
Boyuan Chen,Zhen Ming Jiang +1 more
- 20 May 2017
TL;DR: The problem of how-to-log is studied by characterizing and detecting the anti-patterns in the logging code by encoding them into a static code analysis tool, LCAnalyzer, which has an average recall of 95% and precision of 60% and can be used to automatically detect previously unknown anti- patterns in the source code.
130
A Survey on Automated Log Analysis for Reliability Engineering
TL;DR: A detailed overview of automated log analysis research can be found in this paper, where the authors present several promising future directions toward real-world and next-generation automated logging analysis, including how to assist the writing of logging statements, how to compress logs and how to parse logs into structured event templates.
128
Logram: Efficient Log Parsing Using n-Gram Dictionaries
TL;DR: Logram as mentioned in this paper leverages-gram dictionaries to achieve efficient log parsing and achieves a higher parsing accuracy than the best existing approaches (i.e., at least 10% higher, on average) and also outperforms these approaches in efficiency, achieving 1.8 to 5.1 times faster than the second-fastest approaches in terms of end-to-end parsing time.
111
References
Automatic identification of load testing problems
Zhen Ming Jiang,Ahmed E. Hassan,Gilbert Hamann,Parminder Flora +3 more
- 24 Oct 2008
TL;DR: This paper presents an approach which mines the execution logs of an application to uncover the dominant behavior for the application and flags anomalies which indicate load testing problems with a relatively small number of false alarms.
Replicating MSR: A study of the potential replicability of papers published in the Mining Software Repositories proceedings
Gregorio Robles
- 02 May 2010
TL;DR: Results show that MSR authors use in general publicly available data sources, mainly from free software repositories, but that the amount of publicly available processed datasets is very low.
•Proceedings Article
Log 2 : a cost-aware logging mechanism for performance diagnosis
Rui Ding,Hucheng Zhou,Jian-Guang Lou,Hongyu Zhang,Qingwei Lin,Qiang Fu,Dongmei Zhang,Tao Xie +7 more
- 08 Jul 2015
TL;DR: The experimental results show that Log2 can control logging overhead while preserving logging effectiveness, a cost-aware logging mechanism that is implemented on an open source system as well as a real-world online service system from Microsoft.
Network Versus Code Metrics to Predict Defects: A Replication Study
Rahul Premraj,Kim Herzig +1 more
- 22 Sep 2011
TL;DR: A replication of one such study conducted by Zimmermann and Nagappan on Windows Server 2003 where the authors leveraged dependency relationships between software entities captured using social network metrics to predict whether they are likely to have defects found that network metrics perform significantly better than source code metrics at predicting defects.
An exploratory study of the evolution of communicated information about the execution of large software systems
Weiyi Shang,Zhen Ming Jiang,Bram Adams,Ahmed E. Hassan,Michael W. Godfrey,Mohamed Nasser,Parminder Flora +6 more
TL;DR: This study explores the concept of CI and its evolution by mining the execution logs of one large open source and one industrial software system, and illustrates the need for better trace ability techniques between CI and the Log Processing Apps that analyze the CI.