Closed lread closed 3 months ago
It seems like all that org.apache.commons.jcs3.*
logging could be suppressed and new, specific (useful!) logging from Watson added?
Does this tie in to #68 ?
Ya is certainly related to #68.
Since clj-watson turns off logging via slf4j-nop, we can assume that these logs lines are not redirected through slf4j.
I think by default Apache Commons JCS uses JUL but can be told to use log4j2. Can experiment with log bridges etc. I think we want all logs redirected to a single logging fwk where we control what we want on and off.
Ok @seancorfield, I've got something working locally.
It makes sense to switch from slf4j-nop to something real.
I'll start with logback-classic (can adjust if you prefer something else) with minimal logging config to suppress the noisy org.apache.commons.jcs3.*
.
This will turn on dependency-check logging - which includes logging for #68.
Currently
When clj-watson starts up it emits quite a few log lines, here's an example:
My Take
Because the presentation is noisy and repetitive I am likely to just skip over the entire log. The only thing I see that seems relevant to me is the cache file root directory.
As a user, I ask myself why a tool is telling me things I do not need to know. And then I wonder if maybe I do need to know about these things it is telling me. And then I feel a bit annoyed with the tool when I realize I probably don't.
Proposal
Look into a way to reduce this startup log noise to maybe:
Next Steps
If you agree, I can look into this more and follow up with a PR.