Static Configuration about blackbox_exporter HOT 8 CLOSED

This is not the intended architecture of a Prometheus exporter. Scheduling and service discovery belong with Prometheus, not exporters.

You should run the blackbox exporter beside Prometheus.

from blackbox_exporter.

This would simply be an additional feature alongside the current feature set.

from blackbox_exporter.

Are all exporters intended to run alongside prometheus? Why is the blackbox-exporter a special case?

from blackbox_exporter.

What you request is an explicit non-goal of this exporter.

Are all exporters intended to run alongside prometheus? Why is the blackbox-exporter a special case?

There's very few exporters in this category, currently only SNMP also fits. It's that way as it's impossible to run an exporter on something like a VIP.

from blackbox_exporter.

Why can't the blackbox-exporter have its own explicit service discovery? It would allow it to be even more decoupled from Prometheus which I'm sure was the intent of making it a exporter in the first place.

from blackbox_exporter.

Why can't the blackbox-exporter have its own explicit service discovery?

That is explicitly not the responsibility of an exporter. It's Prometheus's responsibility.

from blackbox_exporter.

It just seems odd that we have extremely specific modules for very specific endpoints, and then pass in dynamic target configuration.

from blackbox_exporter.

That doesn't seem odd to me. You'll want to probe potentially thousands of targets with the same sort of probe.

from blackbox_exporter.