mauricioaniche/logging-analyzer

Logging analyzer. How good are you with logging?

logging-analyzer's Issues

Issues to fix

• support multi catch
• log.debug(a, b, c, d, e)

http://www.slf4j.org/apidocs/org/slf4j/Logger.html

technical ToDo list

At code level:

• Collect log lines
• Log level (debug, info, ...)
• Location of the log (inside an if, else, ...)
• How is the log line? (only string, variables, exception)
• Measure the length of hard-coded string messages in log lines

At commit history level:

• Detect a commit that changed a log line and the change type (added/removed/deleted)
• Detect log level changes (i.e. from info to debug)
• Two log related metrics - 1) #added logs/TPC, #deleted logs/TPC
• Detect a commit that changed a log during a fix
• Identify developer that changed a commit with a log line + qty of log lines changed

Project information:

• Quantity of commits
• Commits per developer (for every commit, print the experience of everyone again)

Other stuff:

• Log the time taken by JDT to compile the ASTs
• Log the time visitors take to visit the ASTs