modifications for log chatter #160
Merged
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.
Please do not delete the repository or close the corresponding issue for this pull request until you have read the below:
I changed the logging properties to set the aliases and versions loggers to level FINE. This will reduce the ENTER, EXIT chatter. We can request the end user to change those logger levels if needed. However, the quality of logs in the aliases is not ideal. Informative loggers at the FINE level should be added to the aliases code. I have yet to find the information I need for an alias issue from the entering,exiting code. Entering,Exiting loggers is about all that aliases logs except for those at INFO and above.
If setting the version and alias loggers to level FINE is acceptable, we can close the issue and delete the repository. I suggest we open another issue for quality of logs in aliases if we need to spend our time on this. Else, we should add loggers as we find the need when troubleshooting issues.
I put loggers into the logging.properties for the more import logger names. This will be helpful to the user since the logger name is not included in the log stream. The user does not know the names or where to in the source to find the names.
The WDT logger names I did not include in the logger properties are as follows:
wlsdeploy.encrypt
wlsdeploy.validate
wlsdeploy.tool.util
wlsdeploy.json
wlsdeploy.archive
wlsdeploy.yaml
wlsdeploy.model
wlsdeploy.translator
wlsdeploy.variables