Skip to content

Rejuvenate logging statement levels #2754

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

khatchad
Copy link

@khatchad khatchad commented Apr 18, 2019

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:

  • Treat CONFIG/WARNING/SEVERE level as a category and not a traditional level, i.e., our tool ignores CONFIG/WARNING/SEVERE log level (setting 1).
  • Never lower the logging level of logging statements within catch blocks (setting 2).
  • The greatest number of commits evaluated: 5000 (setting 3).

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.

@coveralls
Copy link

@khatchad khatchad changed the title Rejuvenate logging statement levels. Rejuvenate logging statement levels Apr 18, 2019
@khatchad
Copy link
Author

Superseded by #2978.

@khatchad khatchad closed this Nov 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants