ANN: Cambium 0.9.2 (Structured logging for Clojure)

Hi, I am happy to announce the availability of Cambium 0.9.2 - Cambium is a structured logging library for Clojure, compatible based on SLF4J/Logback and clojure/tools.logging libraries. https://cambium-clojure.github.io/ The release changelog for various modules[1] are in their respective

Re: [ANN] Cambium - Structured logging for Clojure

On Friday, 1 December 2017 18:18:36 UTC+5:30, oleksand...@zalando.de wrote: > > On Thursday, November 30, 2017 at 3:35:24 PM UTC+1, Shantanu Kumar wrote: >> >> >> I am happy to announce the availability of Cambium, an Open Source >> project for structured logg

Re: [ANN] Cambium - Structured logging for Clojure

On Thursday, November 30, 2017 at 3:35:24 PM UTC+1, Shantanu Kumar wrote: > > > I am happy to announce the availability of Cambium, an Open Source project > for structured logging in Clojure using SLF4j and Logback. > > Details: https://cambium-clojure.github.io/ > Repo

[ANN] Cambium - Structured logging for Clojure

Hi, I am happy to announce the availability of Cambium, an Open Source project for structured logging in Clojure using SLF4j and Logback. Details: https://cambium-clojure.github.io/ Repos: https://github.com/cambium-clojure *Highlights:* - Evolved through two years of production use at Concur

Re: changes in logging in 1.8?

riday, March 11, 2016 at 12:20:44 AM UTC-5, Andy L wrote: > Hi, > > I noticed that after upgrade to Clojure 1.8.0 (from 1.7.0) a weird > occurrence of logging, even during uberjar generation which looks like this, > using lein 2.5.3: > > $ lein uberjar > Compiling co

Re: changes in logging in 1.8?

weird > occurrence of logging, even during uberjar generation which looks like > this, using lein 2.5.3: > > $ lein uberjar > Compiling core > 2016-03-10 22:11:23.030:INFO::main: Logging initialized @964ms > > I believe that actual log is pegged from here > https://github

changes in logging in 1.8?

Something in profiles.clj causing the application to be evaluated? -- 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 yo

changes in logging in 1.8?

Hi, I noticed that after upgrade to Clojure 1.8.0 (from 1.7.0) a weird occurrence of logging, even during uberjar generation which looks like this, using lein 2.5.3: $ lein uberjar Compiling core 2016-03-10 22:11:23.030:INFO::main: Logging initialized @964ms I believe that actual log is pegged

Re: [ANN] unilog 0.7.5: logging should be easy

Looks great. Thanks for sharing. David -- 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 unsubscr

[ANN] unilog 0.7.5: logging should be easy

Hi #clojure, I just released unilog 0.7.5 (previously logconfig). Unilog provides a map-based configuration interface for logback, which will be picked up by clojure.tools.logging, log4j, JuL and commons-logging - the standard JVM logging mechanisms. If you're writing executables (da

Re: [ANN] ring.middleware.logger - Easy Ring Request Logging

These are very useful! Thanks! On Wednesday, October 1, 2014 10:12:06 PM UTC-4, Paul Legato wrote: > > I'm happy to announce ring.middleware.logger > , which logs details > of each Ring request to a file, or to arbitrary functions you provide.

[ANN] ring.middleware.logger - Easy Ring Request Logging

I'm happy to announce ring.middleware.logger , which logs details of each Ring request to a file, or to arbitrary functions you provide. The emphasis is on simplicity -- you can plug it in and go with sane out-of-the-box defaults, without any

Re: setting c3p0 logging

So that's new in 0.9.5? Good to know. We're still on 0.9.2.1. On Aug 9, 2014, at 10:08 AM, Brian Craft wrote: > In case anyone hits the same problem: > > strace showed the file being read, but it was having no effect, and c3p0 > reported no errors in the config. Checking the c3p0 changelog, I f

Re: Can I compare ::logging from one namespace with ::logging from another?

By the way, Keywords in a hierarchy need not be namespaced unless they are in the global hierarchy. user> (def H (-> (make-hierarchy) (derive :klutz :person))) user> (isa? H :klutz :person) true user> (isa? H :eggplant :person) false user> (isa? H :person :klutz) false ;; just to show contras

Re: Can I compare ::logging from one namespace with ::logging from another?

. :: is used in cases where you want to exploit this important >>>> property of keywords, so that your keyword won't e.g. clash with other >>>> keywords in a collection, contents of which you don't know. >>>> >>>> Jozef >>>&

Re: Can I compare ::logging from one namespace with ::logging from another?

On 9 August 2014 21:34, Reid McKenzie wrote: > > My reading of James and Jozef's last emails is that you can use exactly > this model, where you simply invent a prefix for your keywords, the > conventional name for which is a "namespace", and use that rather than > trying to use the :: syntax to

Re: Can I compare ::logging from one namespace with ::logging from another?

Jozef > > > On Saturday, August 9, 2014 7:46:45 PM UTC+2, larry > google groups wrote: > > Please forgive this stupid question, but I'm still > trying to understand exactly what the double &quo

Re: Can I compare ::logging from one namespace with ::logging from another?

not equal to :ns2/foo, nor to just >>>> :foo. :: is used in cases where you want to exploit this important >>>> property of keywords, so that your keyword won't e.g. clash with other >>>> keywords in a collection, contents of which you don't know. >&g

Re: Can I compare ::logging from one namespace with ::logging from another?

d names are equal. :ns1/foo is thus not equal to :ns2/foo, nor to just >>>> :foo. :: is used in cases where you want to exploit this important >>>> property of keywords, so that your keyword won't e.g. clash with other >>>> keywords in a collection, contents o

Re: Can I compare ::logging from one namespace with ::logging from another?

just >>> :foo. :: is used in cases where you want to exploit this important >>> property of keywords, so that your keyword won't e.g. clash with other >>> keywords in a collection, contents of which you don't know. >>> >>> Jozef >>> &g

Re: Can I compare ::logging from one namespace with ::logging from another?

gt;>> Jozef >>> >>> >>> On Saturday, August 9, 2014 7:46:45 PM UTC+2, larry google groups wrote: >>>> >>>> Please forgive this stupid question, but I'm still trying to understand >>>> exactly what the double "::" me

Re: Can I compare ::logging from one namespace with ::logging from another?

;> >> >> On Saturday, August 9, 2014 7:46:45 PM UTC+2, larry google groups wrote: >>> >>> Please forgive this stupid question, but I'm still trying to understand >>> exactly what the double "::" means. I have read that I can use (derive) to

Re: Can I compare ::logging from one namespace with ::logging from another?

t the double "::" means. I have read that I can use (derive) to >> establish a hierarchy and I can imagine how this would be useful for things >> like throwing errors and catching them and logging, but I've also read that >> "::" adds the namespace to the symbol,

Re: Can I compare ::logging from one namespace with ::logging from another?

imagine how this would be useful for things > like throwing errors and catching them and logging, but I've also read that > "::" adds the namespace to the symbol, so I would assume that I can not > match ::logging from one namespace with ::logging from another? > >

Can I compare ::logging from one namespace with ::logging from another?

Please forgive this stupid question, but I'm still trying to understand exactly what the double "::" means. I have read that I can use (derive) to establish a hierarchy and I can imagine how this would be useful for things like throwing errors and catching them and logging, but

Re: setting c3p0 logging

In case anyone hits the same problem: strace showed the file being read, but it was having no effect, and c3p0 reported no errors in the config. Checking the c3p0 changelog, I found I needed to update to the c3p0 prerelease to get slf4j support. Now it's working. On Friday, August 8, 2014 10:1

setting c3p0 logging

I'm trying to get c3p0 to log to slf4j. Anyone have this working? I'm dropping a c3p0.properties file in the "resources" directory, but it's not having any effect. I can't tell if the file is being found. Is there a good way to debug this? -- You received this message because you are subscribe

Re: timbre logging, java libs

tive. GUIs like visualvm are only good for spot-checking, not for logging performance vs. a few thousand use cases, for example, or for keeping a slow-query log. Are there other scriptable profiling solutions? On Friday, July 25, 2014 1:55:49 PM UTC-7, Hugo Duncan wrote: > > > craft..

Re: timbre logging, java libs

craft.br...@gmail.com writes: > Is there any good way to use timbre in a project with java libs, e.g. c3p0, > that use java logging APIs? You might want to look at: http://ptaoussanis.github.io/timbre/taoensso.timbre.tools.logging.html https://github.com/palletops/log-config#user-c

Re: timbre logging, java libs

On Jul 23, 2014, at 7:11 PM, Jonah Benton wrote: > Sean Corfield has a great example of writing a log4j logging backend in > clojure: > > http://corfield.org/blog/post.cfm/real-world-clojure-logging Thanx for the referral. That made me go back and look at what that code has evolve

Re: timbre logging, java libs

Sean Corfield has a great example of writing a log4j logging backend in clojure: http://corfield.org/blog/post.cfm/real-world-clojure-logging On Tue, Jul 22, 2014 at 6:17 PM, Brian Craft wrote: > Is there any good way to use timbre in a project with java libs, e.g. > c3p0, that us

timbre logging, java libs

Is there any good way to use timbre in a project with java libs, e.g. c3p0, that use java logging APIs? Java logging is such a hopeless muddle I don't pretend to understand it, but my impression is that libs like c3p0 use assorted backends (log4j, etc.), which in turn use assorted "

Re: Quick library status updates (logging, Redis, i18n, etc.)

Have had some folks ask about the Carmine appender performance I quoted - the 50k/sec figure is conservative if we're talking about server hardware. If you're not logging awfully large arguments (large state maps, etc.) - you'll basically see standard [unpipelined] Redis write

Re: Quick library status updates (logging, Redis, i18n, etc.)

Hi Colin, Timbre looks quite cool but just a bit surprised to see it using spit. > Surely thats not particularly performant or is there something I'm missing? > Spit does alright in a lot of cases (certainly for prototyping, etc.). The example appenders are there mostly to show how appenders are

Re: Quick library status updates (logging, Redis, i18n, etc.)

e libs that I'm maintaining: > > *Timbre - v3.0.0-RC2 - 2013-12-04* > ====== > Logging & profiling tools > > Major recent changes: > * Carmine (Redis) appender that serializes log entries to length-limited, > rotating lists by log level. A

Re: Quick library status updates (logging, Redis, i18n, etc.)

Thanks Baishampayan, Karsten - appreciate it! -- -- 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. T

Re: Quick library status updates (logging, Redis, i18n, etc.)

00, "Peter Taoussanis" wrote: >> >> Hi all, quick batched update on some libs that I'm maintaining: >> >> Timbre - v3.0.0-RC2 - 2013-12-04 >> == >> Logging & profiling tools >> >> Major recent changes: >>

Re: Quick library status updates (logging, Redis, i18n, etc.)

ining: > > *Timbre - v3.0.0-RC2 - 2013-12-04* > ====== > Logging & profiling tools > > Major recent changes: > * Carmine (Redis) appender that serializes log entries to length-limited, > rotating lists by log level. Allows easy querying+manipulation

Quick library status updates (logging, Redis, i18n, etc.)

Hi all, quick batched update on some libs that I'm maintaining: *Timbre - v3.0.0-RC2 - 2013-12-04* == Logging & profiling tools Major recent changes: * Carmine (Redis) appender that serializes log entries to length-limited, rotating lists by log level. Al

Re: Best Practice For Logging vs. Functional (and Elegant)

ports on what's going on always adds clutter. It's a necessary evil sometimes. For some purposes temporary print/write statements can be deleted later, and for other purposes a debugger is indispensible. For intermittent logging--i.e. when there are only a few places in the whole pro

Re: Best Practice For Logging vs. Functional (and Elegant)

On Tuesday, November 26, 2013 8:56:11 PM UTC+1, Gary Verhaegen wrote: > > I haven't had time to really investigate it, but I was planning to delve > into dire for exactly that problem. > > https://github.com/MichaelDrogalis/dire > > That looks interesting. Thanks for pointing out. Best, stefan

Re: Best Practice For Logging vs. Functional (and Elegant)

I haven't had time to really investigate it, but I was planning to delve into dire for exactly that problem. https://github.com/MichaelDrogalis/dire On Tuesday, 26 November 2013, Stefan Kamphausen wrote: > Hi, > > > logging is a side-effect and I try to keep it out of the func

Best Practice For Logging vs. Functional (and Elegant)

Hi, logging is a side-effect and I try to keep it out of the functional parts of my code. But even for the parts where I want to introduce logging I find that it renders code less readable. As an example, say you've got an 'if-let' somewhere (if-let [a (do-something-non-tr

Re: [ANN] Blackwater 0.0.5 released (SQL query logging)

o confirm, is the recommendation to use this only at development > time? It's been a while since Rails and I don't recall if they turn off SQL > logging in production mode. > > On Friday, August 30, 2013 9:46:43 AM UTC-7, Christopher Allen wrote: >> >> https://gith

Re: [ANN] Blackwater 0.0.5 released (SQL query logging)

recall if they turn off SQL logging in production mode. On Friday, August 30, 2013 9:46:43 AM UTC-7, Christopher Allen wrote: > > https://github.com/bitemyapp/blackwater/ > > Clojure library for logging SQL queries and the time they took for Korma > and clojure.java.jdbc. > >

[ANN] Blackwater 0.0.5 released (SQL query logging)

https://github.com/bitemyapp/blackwater/ Clojure library for logging SQL queries and the time they took for Korma and clojure.java.jdbc. I like having a 'canary in the coal mine' while developing locally so that I can see the queries getting executed and the time they took to run,

Re: [ANN] Library updates (Redis & DynamoDB clients, logging+profiling, i18n+L10n, serialization, A/B testing)

Have had one or two people ask me about this - all libraries are under the EPL v1.0 , the same license as Clojure itself. Cheers! - Peter -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this

[ANN] Library updates (Redis & DynamoDB clients, logging+profiling, i18n+L10n, serialization, A/B testing)

ent changes: sorted set+map support, performance improvements. *Timbre* - logging & profiling library (GitHub<https://github.com/ptaoussanis/timbre> ) Current version: *2.0.0 *- MAJOR RELEASE Clojure dependency: 1.4+ Recent changes: tools.logging support. *Touchstone* - A/B testin

Re: [ANN] Timbre, an all-Clojure logging library

github.com/ptaoussanis/timbre. There've been a number of improvements since the top post, including the addition of a logging profiler and (most recently) the addition of a middleware facility for transforming and filtering log events. For the curious, one way I've been doing my lo

Re: [ANN] Timbre, an all-Clojure logging library

On Fri, Mar 15, 2013 at 7:34 PM, wrote: > I'd just like to thank you for writing this. It's perfect. I'll second that! I've been using Timbre lately and it has been really useful. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this

Re: [ANN] Timbre, an all-Clojure logging library

imbre). > > Features (taken from the readme): > * Small, uncomplicated all-Clojure library. > * Map-based config: no arcane XML or properties files. > * Decent performance (low overhead). > * Flexible fn-centric appender model. > * Sensible built-in appenders including simple email a

Re: ":peer/timeout Transaction timed out", and excessive logging

> structures representing all the facts in the 30M file. Should I be doing > this differently? > > My second thought is perhaps datomic should throttle its logging, since a > million lines of traceback is a bit excessive. It's the same traceback > (about 16 lines) rep

":peer/timeout Transaction timed out", and excessive logging

representing all the facts in the 30M file. Should I be doing this differently? My second thought is perhaps datomic should throttle its logging, since a million lines of traceback is a bit excessive. It's the same traceback (about 16 lines) repeated, only the timestamp changes. -- --

Re: clj-logging-config, lein2 and AOT compilation == NullPointerException

I haven't really found out what the problem is - and haven't been looking into it - but I put a small clojure app together to replicate the issue. You can find it on dropbox[1] I've also updated the issue I had opened on the clj-logging-config github issues page [2] If

clj-logging-config, lein2 and AOT compilation == NullPointerException

Hi all, I've been debugging an issue in my Clojure app deployed on Heroku and after some time I finally tracked it down to what appears to be an issue when AOT compiling the project while using clj-logging-config [1] It works without any issues if I let Clojure compile my namespaces on th

[ANN] Update: Timbre 0.6.0, a (sane) logging library for Clojure

Hi - second promised release for today! Github: https://github.com/ptaoussanis/timbre Clojars: https://clojars.org/com.taoensso/timbre Changes: * Now supports namespace black/whitelist filtering with wildcards. * Now includes a logging-level aware logging profiler based on the old Contrib

Re: [ANN] Timbre, an all-Clojure logging library

Thank you!! I'm glad to know that it's not only me who thought Log4j was a terrible solution for logging in Clojure :) On Mon, May 28, 2012 at 7:17 PM, Peter Taoussanis wrote: > Hi everyone, > > I recently lost it after spending 5+ hours trying to figure out why Log4j >

Re: [ANN] Timbre, an all-Clojure logging library

Done! Having said that, I don't suggest anyone really edit their config line-by-line like this. What I do is create a map of everything I need during environment config and just merge it over the Timbre defaults with something like this: (defn deep-merge-with ; From clojure.contrib.map-utils

Re: [ANN] Timbre, an all-Clojure logging library

Looks good! As you said, logging is just too damn complicated in java. Suggestion: change timbre/config to a function, seems way nicer to call (timbre/config :current-level :warn) rather than (swap! timbre/config assoc :current-level :warn) Jonathan On Mon, May 28, 2012 at 1:17 PM, Peter

[ANN] Timbre, an all-Clojure logging library

ible fn-centric appender model. * Sensible built-in appenders including simple email appender. * Tunable flood control. * Asynchronous logging support. As always, any comments/pull-requests/whatever very welcome! Cheers! - Peter Taoussanis (@ptaoussanis) -- You received this message because you are su

Re: When I use Agents for logging I have a different behavior in the REPL as in the program

I tried it with doseq many times, but the behvior is the same. In the REPL I got a full map of information, but when I use the program the map with the agent logs is empty. Am 22.04.2012 19:51, schrieb Moritz Ulrich: Just a quick guess after a quick glimpse at the code you linked: (map #(se

Re: When I use Agents for logging I have a different behavior in the REPL as in the program

I had made some changes on the code I posted. Here is the actual usedcode with the logging functions included. (ns evolution.genalg (:use [util.time]) (:use [util.profile])) ;; Implementation of a genetic algorithm based on the code given ;; in the book "Clojure" by Stefan Kamp

Re: When I use Agents for logging I have a different behavior in the REPL as in the program

Just a quick guess after a quick glimpse at the code you linked: (map #(send % a-day-in-the-life-agent-fn) domiciles) map is lazy. It doesn't execute anything until you request the result. (do ... (map ...) (foo)) discards the result of map, making it a no-op. This also explains why it works in

When I use Agents for logging I have a different behavior in the REPL as in the program

I wanted to log some information during the execution of the genetic algorithm I posted earlier here. So I chnaged the code and changed the function 'track-evolution' so, that it now accept a maximal runtime and returns a m

Re: clojure libs and logging

10 PM, Keith Irwin > wrote: > > What's the standard way for including logging in a library? I've > > included clojure.tools.logging as a dependency, but the resulting > > jar (lein install), contains clojure.tools.logging classes. Is that > > okay, given any proje

Re: clojure libs and logging

On Mon, Nov 21, 2011 at 9:10 PM, Keith Irwin wrote: > What's the standard way for including logging in a library? I've included > clojure.tools.logging as a dependency, but the resulting jar (lein install), > contains clojure.tools.logging classes. Is that okay, given any proj

Re: clojure libs and logging

I'm guessing that removing the non-project classes and then just declaring a dependency should work well enough. Couldn't find :disable-implicit-clean in the sample project file technomancy maintains on his github repo, but did use :clean-non-project-classes, which removed the compil

Re: clojure libs and logging

Hi, Do you have the :disable-implicit-clean option set to false in your project.clj file ? If not, add it to remove the classes from dependencies that otherwise may pollute your target. As far as "standard" logging in a lib, it might be time to rely on clojure.tools.logging syst

clojure libs and logging

I want to build in some automated reconnect stuff. Normally, I use clojure.tools.logging and add dependencies for log back. Works great. What's the standard way for including logging in a library? I've included clojure.tools.logging as a dependency, but the resulting jar

Re: Re: Re: java logging properties and lein

Okay, thanks. I think the library I interface with is using java.util.logging. I might need to reset the logging configuration. I recall something like that in the past like LogManager.reset(); On , Mark Rathwell wrote: > You still need to load the properties and tell the logger to

Re: Re: Re: java logging properties and lein

Okay, thanks. I think the library I interface with is using java.util.logging. I might need to reset the logging configuration. I recall something like that in the past like LogManager.reset(); On , Mark Rathwell wrote: > You still need to load the properties and tell the logger to

Re: Re: java logging properties and lein

> You still need to load the properties and tell the logger to use them. >  Assuming it is using log4j, something like the following should do > that (completely untested though): > > ... >  (:require [clojure.java.io :as io]) > ... > (with-open [s (io/input-stream (io/resource "logging.properties"

Re: Re: java logging properties and lein

> I put a logging.properties file in the resources directory of the project > but it does not seem to pick it up. Do I have to do something else to > override the default logging from the java library I am using? You still need to load the properties and tell the logger to use them. As

Re: Re: java logging properties and lein

I put a logging.properties file in the resources directory of the project but it does not seem to pick it up. Do I have to do something else to override the default logging from the java library I am using? On , Phil Hagelberg wrote: On Mon, Nov 14, 2011 at 9:22 AM, joegallo joega

Re: java logging properties and lein

On Mon, Nov 14, 2011 at 9:22 AM, joegallo wrote: > You could drop it into the root of src, or you can add a :resources-path > "etc" in your project.clj and then put it in the root of that.  Some purists > would probably argue that the latter is better, but the former should work > just fine, too.

Re: java logging properties and lein

You could drop it into the root of src, or you can add a :resources-path "etc" in your project.clj and then put it in the root of that. Some purists would probably argue that the latter is better, but the former should work just fine, too. -- You received this message because you are subscrib

java logging properties and lein

I'm interfacing with a java library. I'm getting logging info messages. Where do I put the logging.properties file in a lein project? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@g

java logging properties and lein

I'm interfacing with a java library. I'm getting logging info messages. Where do I put the logging.properties file in a lein project? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@g

Re: Problems logging reliably

Sorry, posted the wrong data describing the problem. Here it is. https://gist.github.com/1257122 On Oct 2, 12:39 am, Daniel wrote: > This might be an issue with my log4j properties file, Cake, or > tools.logging, Here's my log4j.properties file:   > https://gist.github.com/1257086 > > It should

[tools.logging] Problems logging reliably

This might be an issue with my log4j properties file, Cake, or tools.logging, Here's my log4j.properties file: https://gist.github.com/1257086 It should back up the current log file into an old, dated version at midnight, and use a new, undated log file. Instead it appears to halt program execut

Logging input

ojure/tools.logging [2] http://clojure.github.com/clojure-contrib/logging-api.html [3] http://clojure.github.com/clojure-contrib/branch-master/logging-api.html -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send e

Re: logging recommendation

We use a combination of apache common logging and log4j. In dev we can remove log4j and still have some decent console logging. Luc P. Dave Newton wrote .. > On Tue, Nov 23, 2010 at 5:46 PM, Stuart Sierra > wrote: > > > On Nov 20, 5:56 pm, HiHeelHottie wrote: > > > W

Re: logging recommendation

On Tue, Nov 23, 2010 at 5:46 PM, Stuart Sierra wrote: > On Nov 20, 5:56 pm, HiHeelHottie wrote: > > What do you recommend for logging, especially to a set of rolling > > files? Simply use log4j? > > I manage with Log4j. The .properties configuration file is annoying >

Re: logging recommendation

On Nov 20, 5:56 pm, HiHeelHottie wrote: > What do you recommend for logging, especially to a set of rolling > files?  Simply use log4j? I manage with Log4j. The .properties configuration file is annoying sometimes, but it works. -S -- You received this message because you are subscri

Re: logging recommendation

On Nov 21, 11:56 am, HiHeelHottie wrote: > What do you recommend for logging, especially to a set of rolling > files?  Simply use log4j? Log4j has been a dead project for a few years now. Try slf4j and logback. -- You received this message because you are subscribed to the Google

logging recommendation

What do you recommend for logging, especially to a set of rolling files? Simply use log4j? -- 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

Re: logging

We use common logging with a thin Clojure layer around it. It allows us to have different behaviors in dev pre-prod and production. We avoid the hassle of configuring log4j in dev. The default implementation (simple logging) is more than enough most of the time. In prod, we specify the log4j

Re: logging

We are speaking of two different things. SLF4J is a facade, like commons-logging (and to some extent c.c.logging). Their intent is to allow *libraries* to make logging calls, but leave the actual logging implementation up to the runtime application. This in principle allows multiple libraries

Re: logging

On Wed, Sep 15, 2010 at 12:23 PM, ataggart wrote: > If you really need logging, then log4j is probably your best bet > anyway. Or SLF4J, which seems to be the way many (most?) java libraries depend on a some logging library. -- You received this message because you are subscribed to the

Re: logging

dency).   If you really need logging, then log4j is probably your best bet anyway. The master branch c.c.logging docs provide a brief log4j configuration to get people going. Though the fact that deps are directly referencing log4j is a bit of a problem since you may not be using log4j, thus to ben

Re: logging

think I'll look into doing something else. Cheers, Jeff On Sep 15, 2:38 am, ataggart wrote: > First, c.c.logging was intended as a wrapper around some java logging > lib.  There's a plethora of them, so I saw no reason to add another. > > As for "simple out of

Re: logging

First, c.c.logging was intended as a wrapper around some java logging lib. There's a plethora of them, so I saw no reason to add another. As for "simple out of the box logging", it's there (sort of) via java.util.logging, and it defaults writing to stdout at INFO level. Tha

logging

Hi, I've been using my own wrapper for Java's built-in logging so far, but today I took a look at clojure.contrib.logging because I would like to start using spy. It really seems like Clojure should have some simple logging out of the box, but this is not the case yet. Can we mak

Re: Contrib Logging change

For now, I just want to get the most useful stuff into git. Patch submitted: http://www.assembla.com/spaces/clojure-contrib/tickets/58 On Jan 13, 5:03 pm, Timothy Pratley wrote: > Hi Alex, > > 2010/1/13 ataggart : > > > You mean dropping it from the level-specific macros such as error and > > fa

Re: Contrib Logging change

Hi Alex, 2010/1/13 ataggart : > You mean dropping it from the level-specific macros such as error and > fatal?  I'm inclined to disagree; being able to access the exception > instance itself is a Good Thing. Yes. You are quite right; preserving the exception is more important. If I understand co

Re: Contrib Logging change

On Jan 12, 4:46 pm, Timothy Pratley wrote: > My thought would be to drop exceptions from normal logging calls. You mean dropping it from the level-specific macros such as error and fatal? I'm inclined to disagree; being able to access the exception instance itself is a Good Thing. I

Re: Contrib Logging change

ataggart writes: > Which is why I added the arglist metadata (shown via doc): > [level fmt & args] [level throwable fmt & fmt-args] Ah, good call. I missed that. Cheers, Chris Dean -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this gro

Re: Contrib Logging change

Alex Taggart writes: > Ok here's what I threw together:  http://gist.github.com/275527 > > It adds both println-style args as well as a formatting version. > > I like the idea of the level-specific convenience macros behaving like > print, but I'd prefer to move the throwable to be an optional fi

Re: Contrib Logging change

My thought would be to drop exceptions from normal logging calls. 1) It wont *break* any code, it may change the log output slightly as the exception is rendered by str or format instead of by the java logging formatter. 2) I think this is least surprising. 3) The exception taking java call

Re: Contrib Logging change

On Jan 12, 12:19 pm, Chris Dean wrote: > One downside of the new macros is that there is now one more check done > at runtime for every use.  There used to be just the impl-enabled? and > now there is a instance? call as well. True. One optimization I could make is to cover the most common case

  1   2   >