Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

logging in v4 #105

Closed
yogthos opened this issue Jun 14, 2015 · 5 comments
Closed

logging in v4 #105

yogthos opened this issue Jun 14, 2015 · 5 comments

Comments

@yogthos
Copy link
Contributor

yogthos commented Jun 14, 2015

I can't seem to get anything to log using version 4, this is what I've got:

(ns timbre-test.core
  (:require [taoensso.timbre :as timbre]
                [taoensso.timbre.appenders.3rd-party.rotor :as rotor]))

(defn -main []
  (timbre/set-config!
    {:min-level :debug
     :enabled? true
     :output-fn timbre/default-output-fn})

  (timbre/merge-config!
    {:appenders
     {:rotor (rotor/rotor-appender  {:path "test.log"})}})

  (timbre/info "HELLO!!!!"))

I imagine I'm missing something obvious here, but based on the docs this looks like it should work. I've tried both with :rotor and without and I'm not seeing a log file being created nor any output in the system out.

@yogthos
Copy link
Contributor Author

yogthos commented Jun 17, 2015

It looks like it might be a problem with the rotor appender, I tried 4.0.1 with a rolling appender and that works as expected.

@ptaoussanis
Copy link
Member

Hi Dmitri, sorry for the delayed reply. It's very likely a bug in the rotor appender; I didn't look too closely at (or test) any of the 3rd-party appenders when migrating stuff to v4.

Just taking a couple days off from GitHub atm; will make this a priority when I'm back at work.

Sorry for the trouble!

@yogthos
Copy link
Contributor Author

yogthos commented Jun 17, 2015

No worries, if I get a chance I'll take a look and let you know what I find. :)

@yogthos
Copy link
Contributor Author

yogthos commented Jun 17, 2015

so turns out it was just the default log level being set to :warn that was screwing it up

@ptaoussanis
Copy link
Member

Closing with 338b952

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants