Feature request: probe to prometheus.io is not helpful, should make options or pulldowns
macetw opened this issue · 2 comments
Host operating system: output of uname -a
Linux tmace-5820 5.4.0-169-generic #187-Ubuntu
blackbox_exporter version: output of blackbox_exporter --version
blackbox_exporter_build_info{branch="HEAD",goarch="amd64",goos="linux",goversion="go1.20.4",revision="0b0467473916fd9e8526e2635c2a0b1c56011dff",tags="netgo",version="0.24.0"} 1
What is the blackbox.yml module config.
(not relevant)
What is the prometheus.yml scrape config.
(not relevant) ...
Feature request
In our use case, which I expect is common for industrial users, network firewalls and network-policies have tight limitations within our kubernetes clusters. Unfortunately, on the main page of Blackbox-exporter, the "prometheus.io" probe cannot succeed. It actually idles for a minute until it breaks.
A better approach would be to allow us to pick a different default-hostname other than prometheus.io -- some hostname that is internal within the company (that is unblocked by network-policy). We'd like to be able to configure that. (and if we can configure that, we need the helm-values to support the new field)
Also in our use case, we have a lot more modules other than http_2xx. We need to check with different certificates. We need to check on different ports. We need to send POST data and with certain headers. The even-better approach would be to have a small HTML form that we can select from a list of modules we have installed and type in a hostname. And the default-text of that hostname would be from what we can configure (or just prometheus.io, if not configured).
For questions/help/support please use our community channels. There are more people available to potentially respond to your request and the whole community can benefit from the answers provided.
Hm, the code for this default probe is hard-coded in main.go. My feature request requires code changes.