Reduce log level of noisy debug messages #192
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.
In order to make debugging and oncall activity easier, I find it nice if activating the filter
log is not 'DEBUG'
in Kibana shows me a good summary overview of what is happening in the system on each runloop. Then, if I actually want to debug a specific loop, I can select the correct time range and drill down (also by showing DEBUG logs).I feel like generally this is the case at the moment. However, upon sending the solution submission I see a lot of noisy alerts and am not really sure these are needed to be show on every run by default (see screenshot)
I therefore propose to downgrade the verbosity of these logs to debug. cc @sunce86 if those logs are still needed (I generally don't mind verbose logs to make debugging easier, but we should make sure they don't make other maintenance harder).