Support basic auth about haproxy_exporter HOT 3 CLOSED

Hey,

to keep the scope of the project limited we won't be supporting authentication in the serving components for the foreseeable future; there are just too many options, and this is better served by putting a reverse proxy in front that is designed for this. This way, the monitoring components can be focused on monitoring alone.

For your use-case, I would bind the exporter to localhost and front it with either HAProxy itself (but beware that you may lose the ability to scrape if it falls over badly) or e.g. nginx. The configuration for that should be very simple. As an added bonus, you can then also use HTTPS.

FWIW, on the scraping side Basic Auth is fully supported, so you will be able to scrape this without further layers.

/MR

from haproxy_exporter.

If that is the general idea, I'm fine with it. I just got the expectation from using the node exporter, which among other things support basic auth out of the box.

/Erik

from haproxy_exporter.

@olcai Oh, interesting point. I almost forgot that node exporter had basic auth. The implementation of that predates the consensus to not implement this in every exporter.

Basic auth without SSL is dangerous, as it looks secure, but isn't. If one then has to put a reverse proxy infront of it anyways to add SSL, that reverse proxy might just as well also take care of the basic auth.

from haproxy_exporter.