Default log level does not match default timbre log level

[johnbendi]

The code here clearly shows this:

slf4j-timbre/src/slf4j_timbre/factory.clj

Lines 12 to 22 in b077afc

	(defn -init
	[]
	(let [default-config (var-get (resolve 'taoensso.timbre/example-config))]
	(when (and (compare-and-set! bootstrapped? false true) (= timbre/*config* default-config))
	(let [level (or (System/getProperty "TIMBRE_LEVEL") (System/getenv "TIMBRE_LEVEL") ":info")]
	(reset! slf4j-timbre.adapter/override-level (keyword (subs level 1))))
	(add-watch #'timbre/*config* ::on-first-config
	(fn [_ _ _ _]
	(reset! slf4j-timbre.adapter/override-level nil)
	(remove-watch #'timbre/*config* ::on-first-config)))))
	[[] (atom {})])

This caused me a lot of problem and valuable time trying to understand why the default setup was not logging at :debug level which is the advertised default for timbre

[pfernandez]

Glad I saw this issue, I don't see TIMBRE_LEVEL anywhere in the timbre docs and was finally able to change the level with export TIMBRE_LEVEL=':warn'.

[rufoa]

I implemented this in #36 (comment) because people had the opposite problem: they started using slf4j-timbre and suddenly the old slf4j default level of info was effectively lowered to debug (timbre's default).

When using libraries like netty, this caused a ton of debug messages to be spewed out before the user could even configure timbre's log level or filtering to shut them up - a problem they didn't have until they started using slf4j-timbre.

We aimed to minimise surprises like this by setting the default level for slf4j-emitted messages to slf4j's default (info), while also not altering the default level for timbre-emitted messages (debug), until the user explicitly configures which level and filters they want. And then we start following that.

So the solution is to explicitly configure timbre's levels in one of the ways they provide (env var, with-level, set-config!, etc etc).

But I recognise this behaviour has caused you both frustration, so I will make sure to document this more prominently in case other people are also running timbre without an explicit config.

[pfernandez]

Thank you, I think a little extra documentation would be helpful. Also note that LOG_LEVEL is legacy and undocumented in timbre, which now uses TAOENSSO_TIMBRE_MIN_LEVEL_EDN instead.

[ptaoussanis]

Hi folks - in case this is still relevant for you, you might want to try Timbre v6.6.0-RC1 which now includes built-in SLF4J(v2) support.