Re: [Shinken-devel] Logging proposition

2012-08-27 Thread nap
On Sat, Aug 18, 2012 at 5:41 PM, Francois Mikus 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,

Re: [Shinken-devel] Logging proposition

2012-08-18 Thread Francois Mikus
On 12-08-18 7:39 AM, Hartmut Goebel wrote: > Am 18.08.2012 06:30, schrieb Francois Mikus: >> 1. Default logging level set to INFO instead of NOTSET which equates >> to DEBUG in reality. >> > I suggest setting the defaullt level to WARNING. "INFO" is much to > verbose, normally one is not int

Re: [Shinken-devel] Logging proposition

2012-08-18 Thread Hartmut Goebel
Am 18.08.2012 06:30, schrieb Francois Mikus: > > 1. Default logging level set to INFO instead of NOTSET which equates > to DEBUG in reality. > I suggest setting the defaullt level to WARNING. "INFO" is much to verbose, normally one is not interested in all this stuff. > 1. Default logging l

[Shinken-devel] Logging proposition

2012-08-17 Thread Francois Mikus
Hello, Here are the proposed changes from less to more controversial: 1. Default logging level set to INFO instead of NOTSET which equates to DEBUG in reality. 2. Default logging level of all INI files set to WARNING. 1. When there is a problem, users usually have a tracefile output,