Feature Request: Support Different Proxies for Individual Targets

[nirmal20081028]

We have a requirement to use different proxy URLs for different targets. Since each target has its own proxy URL, creating multiple scrape jobs based on different proxy URLs is not feasible. We aim to create a single job where both the target and the proxy URL can be passed dynamically.

[mazzz1y]

This is not directly related to blackbox, and it can be resolved by using Prometheus relabeling.

Example:

  - job_name: "blackbox"
    metrics_path: /probe
    labels:
    static_configs:
      - targets: [connectivitycheck.gstatic.com/generate_204]
        labels:
          module: http
      - targets: [connectivitycheck.gstatic.com/generate_204]
        labels:
          module: http_with_proxy
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [module]
        target_label: __param_module
      - source_labels: [__param_target]
        target_label: url
      - target_label: __address__
        replacement: blackbox-exporter:9115

[nirmal20081028]

@mazzz1y ,When managing just a few proxies, it's straightforward. However, with 5,000 targets spread across 5,000 different proxies, how can we effectively handle this using the Blackbox Exporter?

[mahumac]

，当只管理几个代理时，这很简单。但是，由于 5,000 个目标分布在 5,000 个不同的代理中，我们如何使用 Blackbox Exporter 有效地处理这个问题？

Single Prometheus job for dozens of Blackbox exporters | by Hayk Davtyan | Geek Culture | Medium

refer to this document, which is a detailed introduction and should be the effect you need