<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Mar 1, 2016 at 10:33 AM, Rob Brucks <span dir="ltr"><<a href="mailto:rob.brucks@rackspace.com" target="_blank">rob.brucks@rackspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But then why write the slony daemon log file at all?<br>
<br>
No timestamps means you have to go look in the syslog file anyway.</blockquote><div><br></div><div>I was involved in syslog support, and Steve's thoughts seem</div><div>to fit the intent pretty well.</div><div><br></div><div>If you use syslog, it independently captures timestamps, and likely more accurately </div><div>than slon logs would (think of the case of aggregating logs across servers; syslog </div><div>would handle coordinating times and merging into one big log).</div><div><br></div><div>As Steve mentioned, you wouldn't want to collect two timestamps in each line,</div><div>much preferable to just have one.</div><div><br></div><div>The place where we decided to simplify was to have just one representation to</div><div>control contents of log entries, and thus fewer configuration parameters. In order</div><div>to have timestamps in slon's STDOUT/STDERR logs, and leave them out for syslog, we'd</div><div>need more configuration parameters, and it is commonly thought that we've</div><div>already got plenty of configuration.</div><div><br></div><div>My attitude at the time was that if you decide to request using syslog, then</div><div>that presumably was how you wanted to handle monitoring, and that</div><div>the STDOUT/STDERR logs become of little importance.<br></div><div><br></div><div>If it's of huge importance to have separate formatting of syslog and native</div><div>logging, we could do so. But my first reaction is to ask why you're keen on</div><div>the native logging when syslog lends so much greater flexibility.<br></div><div><br></div><div>We didn't make them mutually exclusive, because it seemed easy</div><div>enough to provide both in a form. But if it takes a lot more sophisticated</div><div>configuration to make them useful, well, I'd rather point sophisticated</div><div>configuration attentions at doing fancier things with syslog.</div></div></div></div>