Logging in Java with the JDK 1.4 Logging API and Apache log4j

Gupta, Samudra

doi:10.1007/978-1-4302-0765-8

Cited by 3 publications

(2 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Logging in an application is a systematic and controlled way to represent the condition of an application so that it can be understood by humans [4]. A log can record various events that occur when the application is running.…”

Section: Loggingmentioning

confidence: 99%

Implementation of Logging Feature in Android Payment SDK using Scrum Method

Rifai

Ramadhani

2021

IJISTECH

View full text Add to dashboard Cite

Electronic money or e-money is a technological innovation that allows payment transaction processing to be easier and more practical. PT Aino Indonesia is a payment gateway company that serves payment processes using this technology for various business segments. To satisfy the requirements of each business segment, Aino needs to develop a wide range of applications. These applications require a standard for the payment system to make it faster to integrate and maintain. The payment team at Aino has developed a module or SDK that provides a standard payment system for Android-based applications. Two new features will be added to this SDK, the logging feature and log file upload. The logging feature will record the data generated by each transaction process into a log file. Next, the SDK will upload the log files to the server to help retrieve transaction data uploaded from the device. Both features will help the process of tracking issues and problems that may arise during the transaction process. The development of the two features in this SDK uses the Scrum method to ensure it stays on track.

show abstract

Section: Loggingmentioning

confidence: 99%

Implementation of Logging Feature in Android Payment SDK using Scrum Method

Rifai

Ramadhani

2021

IJISTECH

View full text Add to dashboard Cite

show abstract

“…However, they have limited instrumentation capabilities for user-space instrumentation, and incur a high overhead due to frequent kernel context-switches and complex trampoline mechanisms. Hence, software developers often utilize program print statements, write their own loggers, or use tools like log4j [9] or log4c [10] to track the execution of their applications. However, while they have low-overhead they are inflexible and can only be turned on/off at compiletime or before starting the execution, thereby greatly reducing their effectiveness.…”

Section: Introductionmentioning

confidence: 99%

iProbe: A lightweight user-level dynamic instrumentation tool

Arora

Zhang

Rhee

et al. 2013

2013 28th IEEE/ACM International Conference on Automated Software Engineering (ASE)

View full text Add to dashboard Cite

We introduce a new hybrid instrumentation tool for dynamic application instrumentation called iProbe, which is flexible and has low overhead. iProbe takes a novel 2-stage design, and offloads much of the dynamic instrumentation complexity to an offline compilation stage. It leverages standard compiler flags to introduce "place-holders" for hooks in the program executable. Then it utilizes an efficient user-space "HotPatching" mechanism which modifies the functions to be traced and enables execution of instrumented code in a safe and secure manner. In its evaluation on a micro-benchmark and SPEC CPU2006 benchmark applications, the iProbe prototype achieved the instrumentation overhead an order of magnitude lower than existing state-of-theart dynamic instrumentation tools like SystemTap and DynInst.

show abstract