2019 IEEE International Conference on Software Maintenance and Evolution (ICSME) 2019
DOI: 10.1109/icsme.2019.00022
|View full text |Cite
|
Sign up to set email alerts
|

An Approach to Recommendation of Verbosity Log Levels Based on Logging Intention

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
11
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 18 publications
(11 citation statements)
references
References 19 publications
0
11
0
Order By: Relevance
“…Both studies highlight the relationship of the log message and associate severity of a log statement. In another study, Anu et al (2019) also proposes a classifier for log level recommendation. They focus on log statements located on if-else blocks and exception handling.…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…Both studies highlight the relationship of the log message and associate severity of a log statement. In another study, Anu et al (2019) also proposes a classifier for log level recommendation. They focus on log statements located on if-else blocks and exception handling.…”
Section: Resultsmentioning
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%
“…Our approach is reasonably extendable to predict LVL and VAR alongside the LSD suggestion. Since we have access to the source code of the method that we are predicting the logging statement for and its clone pair, a reasonable starting point is to suggest the same LVL as of its clone pair, and then augment it with additional learning approaches such as [12,45,48] for more sophisticated LVL prediction. For example, our analysis for the evaluated projects in Figure 5 shows that code clones match in their verbosity levels in the range of (92, 97)%.…”
Section: Discussionmentioning
confidence: 99%
“…J stands for journal, and C stands for conference, symposium, or workshop. The list of additional venues with only one publication include: arXiv [123], [124], CSUR [65], TOCS [67], TPDS [125], IEEE Software [57], TSMCA [126], TNSM [127], SP&E [128], JCST [129], HiPC [130], CSRD [131], IJCAI [132], NSDI [7], CIKM [133], CCS [5], SIGKDD [134], IMC [135], MASCOTS [136], WSE [137], IWQoS [138], ICWS [139], ICPC [140], ICSEM [141], ICPE [142], ICC [143], Middleware [144], VLDB [15], CNSM [13], APSYS [145], HICSS [146], and COMPSAC [147].…”
Section: Logging Challengesmentioning
confidence: 99%
“…Anu et al [141] -Proposes a method to make the logging level decisions by understanding the logging intentions.…”
Section: Asmentioning
confidence: 99%