errors while scraping syslog-ng about syslog_ng_exporter HOT 10 CLOSED

@brandond any help please ?

thank you in advance

from syslog_ng_exporter.

Did you mount the syslog-ng.ctl socket into the container at the appropriate path?

from syslog_ng_exporter.

from syslog_ng_exporter.

Hmm. Is there anything interesting in the syslog-ng logs? Not exactly sure what connection refused means on a unix socket.

from syslog_ng_exporter.

syslog-ng logs really doesn't help .. i have only restart/ reload messages :(

from syslog_ng_exporter.

syslog-ng versin :

syslog-ng 3 (3.33.2)

from syslog_ng_exporter.

Can you show how you've mounted the socket into the container? I suspect that the path just isn't right and you're not actually connecting to syslog-ng at all.

from syslog_ng_exporter.

ok, see below screens

how i run docker container

from syslog_ng_exporter.

You appear to be mounting the binary at /usr/sbin/syslog-ng-ctl into the container, instead of the actual syslog-ng control socket. The cli tool binary is not the control socket. Find the syslog-ng control socket and mount that in. Most distros place the socket at /var/lib/syslog-ng/syslog-ng.ctl, which is the default used by this tool.

This is actually covered in the example in the readme, I'm curious why you are trying to mount the binary in instead?
https://github.com/brandond/syslog_ng_exporter/blob/master/README.md#using-docker

from syslog_ng_exporter.

you're right
now exporter works fine :)

@brandond thank you for your helps :)

from syslog_ng_exporter.