<div dir="ltr"><br><br><div class="gmail_quote">2008/9/18 Duncan Turnbull <span dir="ltr"><<a href="mailto:duncan@e-simple.co.nz">duncan@e-simple.co.nz</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Its a good question<br>
<br>
I have lots of disk space so leave it high, I would rather have the<br>
detail if I need it<br>
<br>
It probably would seem sensible to revisit stable systems after a year<br>
and lower the verbosity, but then since I can afford the space I am not<br>
too fussed.<br>
<br>
Cheers Duncan</blockquote><div> </div><div><br>Once, a customer of mine asked one employee's calls listing.<br>When I read CDR, I discovered most of it was unusable, due to a mistake in dialplan.<br><br>Then, I was very happy to use logs as a second source of CDR : I could parse logs to complement CDR and provide the listing I was asked.<br>
<br>At that time, I told myself I should think it over and elaborate some rule about logging verbosity.<br><br>So at the moment, I told myself I would "never set verbosity any lower to the point you wouldn't be able to rebuild CDR from it".<br>
<br>Another thought is the other day, when I tried to shrink customer's logs, after 30mn of processing, I got "temperature is becoming too hot" warning in syslog. So I didn't take any chance and stopped the ongoing job.<br>
So having plenty (too much) of logs has a price as I couldn't save them as conveniently as I would have thought.<br></div></div></div>