Yep but how do you get that to a d_es destination without adding an external tool ? My understanding of the purpose is that stats may stop getting updated if the pipeline fails so It needs to be a separate "thread" but seems like that would be handled in separate src and destination definitions ? i.e. Keep your stats/monitoring separate from the data stream. On Mon, Oct 16, 2017 at 11:43 AM, james.r.hendrick < james.r.hendrick@gmail.com> wrote:

Do you mean the internal stats facility? I would look into the elasticsearch native destination if you are not already.

Jim

Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message -------- From: Evan Rempel <erempel@uvic.ca> Date: 10/16/17 11:01 AM (GMT-05:00) To: syslog-ng@lists.balabit.hu Subject: Re: [syslog

I have a perl script that collects some stats and logs them to syslog again. The syslog stream gets sent to ES, so they end up there, but as a syslog line, not a specific statistic item for things like grafana.

On 10/15/2017 05:57 PM, Scot wrote:

...

Hi,

Looked around for a few hours and didn't see anything.

Has anyone worked on sending syslog-ng stats to ES ? I see several ways I could but wondering if anyone has already. A push method directly from syslog-ng would be awesome.

Scot

____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/? product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq

____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/? product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq