Configuring Blackbox Exporter calls all via file_sd_configs

[Ryuzavi]

Hey

I'm currently exploring Blackbox Exporter to use as out endpoint health checker.  We already use prometheus for some other stuff such as node, jmx, haproxy and so on.  

We use the file_sd_config mechanism heavily to dynamically update prometheus server with new instances to call.  We upload a file per instance that contains the targets for node, jmx and so on.  

Looking at everything available for the Blackbox exporter though it's a little different in that Prometheus itself has the list of URLs to call that it passes to Blackbox Exporter.  As such all the examples show updating the main prometheus file (which isn't viable for us as we have a lot of instances all uploading their own self contained config to prometheus via files).

So I guess I have 2 questions...

1. Is there any way to define blackbox exporter calls fully within files_sd_config files?

2. Or, if not, is there instead another exporter that can be configured independently to check various endpoints on it's own that prometheus can then come in and collect the results of?

Cheers,

R.

[Julius Volz]

On Mon, Sep 3, 2018 at 4:11 PM, Ryuzavi <grant...@verint.com> wrote:

Hey

I'm currently exploring Blackbox Exporter to use as out endpoint health checker.  We already use prometheus for some other stuff such as node, jmx, haproxy and so on.  

We use the file_sd_config mechanism heavily to dynamically update prometheus server with new instances to call.  We upload a file per instance that contains the targets for node, jmx and so on.  

Looking at everything available for the Blackbox exporter though it's a little different in that Prometheus itself has the list of URLs to call that it passes to Blackbox Exporter.  As such all the examples show updating the main prometheus file (which isn't viable for us as we have a lot of instances all uploading their own self contained config to prometheus via files).

So I guess I have 2 questions...

1. Is there any way to define blackbox exporter calls fully within files_sd_config files?

The Blackbox targets to probe (like "https://google.com") can come from file_sd (or any other SD), no problem. You still need a scrape config in the Prometheus config that actually scrapes the Blackbox exporter, but it can get targets to probe from file_sd. You can even vary the Blackbox Exporter probe module to use for each target by setting a "__param_module" hidden label on each target to override any "module" HTTP param that is set in the scrape config itself.

 

2. Or, if not, is there instead another exporter that can be configured independently to check various endpoints on it's own that prometheus can then come in and collect the results of?

Cheers,

R.

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsubscribe@googlegroups.com.
To post to this group, send email to prometheus-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/c7cc85ef-75e6-4075-95aa-4a41aaf532f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[grant...@verint.com]

Ok thanks Julius, will give that a go.

On Monday, 3 September 2018 15:21:08 UTC+1, Julius Volz wrote:

On Mon, Sep 3, 2018 at 4:11 PM, Ryuzavi <grant...@verint.com> wrote:

Hey

I'm currently exploring Blackbox Exporter to use as out endpoint health checker.  We already use prometheus for some other stuff such as node, jmx, haproxy and so on.  

We use the file_sd_config mechanism heavily to dynamically update prometheus server with new instances to call.  We upload a file per instance that contains the targets for node, jmx and so on.  

Looking at everything available for the Blackbox exporter though it's a little different in that Prometheus itself has the list of URLs to call that it passes to Blackbox Exporter.  As such all the examples show updating the main prometheus file (which isn't viable for us as we have a lot of instances all uploading their own self contained config to prometheus via files).

So I guess I have 2 questions...

1. Is there any way to define blackbox exporter calls fully within files_sd_config files?

The Blackbox targets to probe (like "https://google.com") can come from file_sd (or any other SD), no problem. You still need a scrape config in the Prometheus config that actually scrapes the Blackbox exporter, but it can get targets to probe from file_sd. You can even vary the Blackbox Exporter probe module to use for each target by setting a "__param_module" hidden label on each target to override any "module" HTTP param that is set in the scrape config itself.

 

2. Or, if not, is there instead another exporter that can be configured independently to check various endpoints on it's own that prometheus can then come in and collect the results of?

Cheers,

R.

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.

[grant...@verint.com]

Another thing I was wondering about is that since it's done at the prometheus config level it would be more awkward to set up multiple blackbox exporters to spread out the load...  I have a lot of endpoints to monitor and an exporter like the rest that was independent, polled itself and gave results would suit my infrastructure more I think.