2019
DOI: 10.1007/s10664-019-09757-y
|View full text |Cite
|
Sign up to set email alerts
|

Guiding log revisions by learning from software evolution history

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

1
15
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 13 publications
(16 citation statements)
references
References 26 publications
1
15
0
Order By: Relevance
“…Nguyen et al used Jsync to track cloned code in the software evolution process [28]. Moreover, many studies used GumTree to analyze code patterns of changes such as bug-fixing changes [5], [13], [18], [21], [23], [29], logging changes [22] and changes to online code examples [34]. Also, prior work trained models based on the edit actions of changes that are calculated using GumTree [7], [15], [24], [31], [32].…”
Section: B Use Of Ast Mapping Algorithmsmentioning
confidence: 99%
See 2 more Smart Citations
“…Nguyen et al used Jsync to track cloned code in the software evolution process [28]. Moreover, many studies used GumTree to analyze code patterns of changes such as bug-fixing changes [5], [13], [18], [21], [23], [29], logging changes [22] and changes to online code examples [34]. Also, prior work trained models based on the edit actions of changes that are calculated using GumTree [7], [15], [24], [31], [32].…”
Section: B Use Of Ast Mapping Algorithmsmentioning
confidence: 99%
“…Also, prior work trained models based on the edit actions of changes that are calculated using GumTree [7], [15], [24], [31], [32]. Such models are used to recommend changes such as patches [32] and logging changes [22]. Different from them, we focus on evaluating AST mapping algorithms instead of using the algorithms to analyze changes.…”
Section: B Use Of Ast Mapping Algorithmsmentioning
confidence: 99%
See 1 more Smart Citation
“…The approach leverages execution logs without instrumenting the code because instrumentation overhead is not possible in a fast evolving production software [31]. Nevertheless, execution paths are successfully captured from the existing logs because in practice, sufficient logging is done to facilitate runtime monitoring [6] [16].…”
Section: Proposed Approachmentioning
confidence: 99%
“…,Chen & Jiang (2017b),Shang et al (2014),Shang, Nagappan & Hassan (2015),Pecchia et al (2015),Kabinna et al (2016),,Zeng et al (2019) to log, where to log, and how to logChen & Jiang (2017a),Hassani et al (2018),Fu et al (2014a),Zhu et al (2015),Li et al (2018),Li, Shang & Hassan (2017),He et al (2018a),Li et al (2019a),Liu et al (2019b),Anu et al (2019),Zhi et al (2019) 11Log Infrastructure: Techniques to enable and fulfil the requirements of the analysis process 16Parsing Extraction of log templates from raw log dataAharon et al (2009), Makanju, Zincir-Heywood & Milios (2009), Makanju, Zincir-Heywood & Milios (2012), Liang et al (2007), Gainaru et al (2011), Hamooni et al (2016), Zhou et al (2010), Lin et al (2016), Tang & Li (2010), He et al (2016a), He et al (2018b), Zhu et al (2019), Agrawal, Karlupia & Gupta (2019) 13 Storage Efficient persistence of large datasets of logs Lin et al (2015), Mavridis & Karatza (2017), Liu et al (2019a) 3 Log Analysis: Insights from processed log data 68 Anomaly detection Detection of abnormal behaviour Tang & Iyer (1992), Oliner & Stearley (2007), Lim, Singh & Yajnik (2008), Xu et al (2009b), Xu et al (2009a), Fu et al (2009), Ghanbari, Hashemi & Amza (2014), Gao et al (2014), Juvonen, Sipola & Hämäläinen (2015), Farshchi et al (2015), He et al (2016b), Nandi et al (2016), Du et al (2017), Bertero et al (2017), Lu et al (2017), Debnath et al (2018), Bao et al (2018), Farshchi et al (2018), Zhang et al (2019), Meng et al (2019) 20 Security and privacy Intrusion and attack detection Oprea et al (2015), Chu et al (2012), Yoon & Squicciarini (2014), Yen et al (2013), Barse & Jonsson (2004), Abad et al (2003), Prewett (2005), Butin & Le Métayer (2014), Goncalves, Bota & Correia (2015) 9 Root cause analysis Accurate failure identification and impact analysis Gurumdimma et al (2016), Kimura et al (2014), Pi et al (2018), Chuah et al (2013), Zheng et al (2011), Ren et al (2019) 6 Failure prediction Anticipating failures that leads a system to an unrecoverable state Wang et al (2017), Fu et al (2014b), Russo, Succi & Pedrycz (2015), Khatuya et al (2018), Shalan & Zulkernine (2013), Fu et al (2012) 6 Quality assurance Logs as support for quality assurance activities Andrews (1998), Andrews & Zhang (2000), Andrews & Zhang (2003), Chen et al checking Ulrich et al (2003), Mariani & Pastore (2008), Tan et al (2010), Beschastnikh et al (2014), Wu, Anchuri & Li (2017), Awad & Menasce (2016), Kc & Gu (2011), Lou et al (2010), Steinle et al (2006), Di Martino, Cinque & of systems (e.g., reliability, performance) Banerjee, Srikanth & Cukic (2010), Tian, Rudraraju & Li (2004), Huynh & Miller (2009), El-Sayed & Schroeder (2013), Ramakrishna et al (2017), Park et al (2017)6Log pl...…”
mentioning
confidence: 99%