On Sat, Aug 18, 2012 at 5:41 PM, Francois Mikus <fmi...@acktomic.com> wrote:
> [..]
> >>
> > There may (I don't know yet) be better ways to achieve this.
> >
> > Before implementing, please what some days. I'm already working on a new
> > logging module, but need to implement performance-tests.
> As mentioned earlier, this is outside of the log.py module.
> There is also something in the standard logging module that permits the
> identification of a namespace.
>
> arbiter.daemon.blah
>
> Which is passed as an option instead of embedding the source of the
> message in the message itself. I have not dug too deep in how it works.
> Not sure of the implications.
>
> Thank you for the response.
>
> X
>
> Hi,
Looks great for less default verbosity. One thing is the [file] atc. Most
[NAME] are in fact the satellite names, so we know in the global log file
that the probel came from this distant scheduler and not the other one. I
don't know what "[file]" will really give us a new information in the end
(we do not have lot of common error text every where I think).
Jean
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
