prometheus/blackbox_exporter

Blackbox prober exporter

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 11th, 2026
Created on September 5th, 2015
Open Issues & Pull Requests: 174 (+0)
GitHub issues: Enabled
Number of forks: 1,217
Total Stargazers: 5,871 (+0)
Total Subscribers: 60 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.3 days
Mean response time: 180.7 days
90th percentile: 663.9 days
Tracked items: 211

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 6% of issues opened in the past year have been closed. Three people close 87% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 73
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 908 days
Stale 30+ days: 62
Stale 90+ days: 58

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (2)
  • enhancement (2)
  • feature-request (2)
  • help wanted (2)
  • duplicate (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Blackbox exporter is a Prometheus exporter that probes endpoints over HTTP, HTTPS, DNS, TCP, ICMP, and gRPC to generate metrics about their availability and performance.

The tool solves the problem of monitoring external services and endpoints that cannot be directly instrumented. Rather than relying on application metrics, blackbox exporter performs active probing from the outside in, sending requests to targets and measuring whether they succeed and how long they take. It exposes results as Prometheus metrics including probe_success and probe_duration_seconds, allowing operators to track endpoint health and response times. The exporter can be deployed as a standalone binary or Docker container and configured with a YAML file to define different probe modules for various protocols and requirements.

Teams should adopt blackbox exporter when they need to monitor external services, third-party APIs, or any endpoint where instrumenting the application itself is not possible. It suits projects that already use Prometheus and want to extend monitoring beyond internal metrics. The tool is particularly valuable for measuring probe timeout ratios against scrape intervals, helping operators understand whether their monitoring windows are sufficient. It supports TLS and basic authentication for securing the exporter's HTTP endpoints, and provides separate logging controls for application logs and prober-specific logs, allowing fine-grained visibility into probe operations.

The project receives issue reports primarily from its user base rather than from core maintainers, indicating substantial real-world adoption. Responses to issues and pull requests typically arrive within one to two weeks. Development activity centers on bug fixes, enhancements, and feature requests, reflecting a focus on stability and incremental improvement of the existing probe capabilities.