I wrote a few more words to describe the motivation behind logconfig: http://spootnik.org/entries/2014/10/15_easy-clojure-logging-set-up-with-logconfig.html
On Tue, Oct 14, 2014 at 11:17 PM, Pierre-Yves Ritschard <p...@spootnik.org> wrote: > Hi, > > While clojure.tools.logging does a great job at logging, writing programs > in clojure involves > setting up the logging, which for people not familiar with the JVM can > mean a lot of head scratching before figuring out how log4j.properties work > and can be fed to a JVM. > > logconfig was meant to help in this scenario, allowing external > log4j.properties to exist if need be > but defaulting to a simpler method which can coexist with the > application's main configuration method. > > logconfig provides a simple map-based config (which you might deserialize > from a YAML/Json/EDN configuration file, or elsewhere) and supports console > appenders as well as timebased rolling appenders, pattern layout and json > layouts for easy interaction with syslog-ng, logstash and friends. > > https://github.com/pyr/logconfig > http://pyr.github.io/logconfig > > Hope this helps! > > - pyr > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
