Prometheus Blackbox Exporter

github.com ↗

Probe HTTP, HTTPS, DNS, TCP, ICMP, and gRPC endpoints and expose results for Prometheus to scrape.

SI Score
80/100
Pricing
Open Source AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about Prometheus Blackbox Exporter

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Prometheus Blackbox Exporter homepage

What it does

Blackbox Exporter is a Prometheus exporter that performs active probes against network targets. Prometheus passes a target and probe module to the exporter, then scrapes metrics such as probe success and duration. The project supports HTTP, HTTPS, DNS, TCP, ICMP, and gRPC probing, with settings defined in YAML modules.

Use the multi-target exporter pattern when you want to check an endpoint from the network location where the exporter runs. Define a probe module, have Prometheus request the exporter for a target, and inspect the resulting probe metrics. An HTTP check can validate that a URL responds, while DNS or TCP modules answer different reachability questions. The official guide also shows how relabeling turns a target list into probe requests.

Blackbox Exporter does not provide a dashboard or incident-notification service by itself; Prometheus must scrape the probe metrics and alerting belongs in the surrounding stack. Its configuration documentation notes that probing makes a single connection attempt rather than retrying like a typical end-user client. If a check needs retries or a richer browser journey, choose another monitor type or build that behavior explicitly.

Strengths

  • Probes multiple network protocols and exports standard Prometheus metrics.
  • The multi-target pattern checks remote endpoints without installing an agent on every target.
  • The official repository uses Apache-2.0 and publishes releases.

Watch out for

  • Prometheus must scrape the exporter; it is not a complete dashboard or alerting platform.
  • A probe makes one connection attempt and does not implement end-user-style retry behavior.

Best for

  • Checking public endpoints or service ports from a chosen network location
  • Adding synthetic availability signals to an existing Prometheus deployment

Sources