Am 13.01.2015 um 07:00 schrieb Hern��n Morales Durand <hernan.morales@gmail.com>:

First of all, I am not the developer of Log4s, but I have been using it for a while and I see no significant gain switching to SystemLogger or ZnLogEvent. As Alain said, it is based in Log4j, which has his own Wikipedia page: http://en.wikipedia.org/wiki/Log4j

I don't think there is too much sense in having "Log Objects" around, where probably I want to tail a daily rolled log from a headless remote image. I read the documentation of SystemLogger hoping to find a mechansim which dynamically selects compression strategies based in what's logged, or some other advanced feature, but I didn't found any :(

if your only concern is to have syslog style logging (maybe even just file based) than all of what we've done is not of any value. If you peek at current logging trends you will see things like logstash et al. In those log collectors they provide huge parsing libraries just to be able to parse every available log format out there in order to produce objects from it that you can store in e.g. elasticsearch. Especially if you have GBs of logging information it makes sense to be able to query the log information for things you are interested in. So think about moving the DEBUG quality from the logger to the viewer of the log.

I personally do enjoy using SystemLogger. Instead of a huge logging framework and the need to parse them back into a system like logstash I did a shortcut by emitting the log objects and send them as json into a elasticsearch database. From there I have queries for finding problems and second I produce stats from it that give me some insight of the health of the system. To me there a plenty of advantages to do it that way. From a simple (well :) ) query I can see something like this.

This things are important for me. 

Norbert

 

So if Object logging is implementing #asLog and #logClass methods maybe I should add them so Log4s can log "Object" :). But seriously, such comparison is not fair. Let's compare real logging features: priorities, levels, appenders, output destinations, hierarchical logging, formatting layout, etc. Many of them are implemented in Log4s.

Cheers,

Hern��n

2015-01-12 14:56 GMT-03:00 Sven Van Caekenberghe <sven@stfx.eu>:

> On 12 Jan 2015, at 18:27, Alain Rastoul <alf.mmm.cat@gmail.com> wrote:
>
> hi all,
>
> Googling a bit for a logging framework in Pharo, I found sl4j, which sounds  familiar to me.
> http://ss3.gemstone.com/ss/Log4s.html/Wiki
>
> I suppose the API is the same as the java package, as claimed by the project page.
> I wonder if anybody is using it , or has tried it and have an advice on that package ?
> (I  saw there was no test and no comments ... :( )
>
> I think it could be great for Pharo to have a standard package like that, a logging facility is mandatory for most -if not all- applications
>
> Any advice or pointers ?

Object logging instead of String logging is the way to go. SystemLogger, Beacon, Zinc's ZnLogEvent are examples. Search the mailing list for past discussions.

> TIA
> --
> Regards,
>
> Alain
>
>