<div dir="auto">I would follow the files using the wildcard-file() source, possibly with marking them up with apache specific name-value pairs that we extract from filenames and/or content.</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Mar 26, 2019, 06:48 Nik Ambrosch <<a href="mailto:nik@ambrosch.com">nik@ambrosch.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>How are people managing their apache access logs using syslog-ng these days - still just piping through logger?  I'm looking to take over logging entirely using syslog-ng, not just reading files from disk and sending to ES or something.<br></div><div><br></div><div>In the past I've used cronolog, which works fine, but I'd love the flexibility of sending the logs through syslog-ng.<br></div></div>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" rel="noreferrer noreferrer" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" rel="noreferrer noreferrer" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer noreferrer" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
<br>
</blockquote></div>