Rejuvenate logging statement levels #2754
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduction
We are in the process of evaluating our research prototype Eclipse plug-in that "rejuvenates" log statement levels based on how "interesting" the enclosing methods are to the developers. The assumption is that methods that are worked on more and more recently by developers should have higher log levels (e.g., INFO as compared to FINEST). Our end goal is to reduce information overload, as well as alleviate developers from manually making log level changes.
The transformation decision is made by analyzing the "degree of interest" (DOI) values of enclosing methods for logging invocations. DOI value is a kind of real number for a program element which shows how developers are interested in it. It is computed from the interaction events between developer and element, such as developer edits the element. In this project, we compute the DOI using the project's git history.
We are looking for feedback on our tool from developers. If you can, we would appreciate if you can comment on each of the transformations in the case that this PR is not accepted. Of course, we would also love to contribute to your project.
Settings
We have several analysis settings . We can vary these settings and rerun our if you desire. The settings we are using in this pull request are:
The head at time of analysis was: 9ce52a2
Notes
We manually initialized two variables to
null
in a test class because the compiler in Eclipse was complaining about them. We can revert this change if you desire.OCA
I signed and emailed the OCA to Oracle. I am also providing a written acceptance of the OCA line:
I am signing on behalf of myself as an individual and no other person or entity, including my employer, has or will have rights with respect my contributions.