Prometheus blackbox exporter metrics show whether an endpoint probe succeeded, how long the probe took, and what HTTP status code came back. Building a Grafana dashboard from those metrics gives operators one place to watch endpoint availability and response latency without opening Prometheus for each target.
Grafana reads the metrics through a Prometheus data source, and each panel runs a PromQL expression against labels such as job and instance. A focused dashboard can start with probe_success, probe_duration_seconds, probe_http_status_code, and probe_http_duration_seconds before adding variables or alert links.
The Prometheus data source must already return blackbox probe series before dashboard work begins. Confirm one target first, then save and reopen the dashboard; a completed view should show Up, an HTTP code such as 200, and recent duration lines for the selected time range.
probe_success{job="blackbox"}
The result should include an instance label and a value of 1 for a reachable target. If no series appears, fix the Prometheus scrape job before building panels.
Tool: Prometheus Scrape Config Generator
The data source must be reachable from Grafana and should already pass a saved connection test.
Related: How to add a Prometheus data source in Grafana
probe_success{job="blackbox"}
Replace job="blackbox" with the label matcher used by the scrape job, such as a different job value or an instance matcher for one endpoint.
Blackbox exporter returns probe_success as 1 when the selected module succeeds and 0 when the probe fails.
probe_duration_seconds{job="blackbox"}
Set the unit to seconds and use the instance label in the legend so each probed endpoint is identifiable on the chart.
Related: How to create a time series panel in Grafana
probe_http_status_code{job="blackbox"}
Use this panel only for HTTP or HTTPS modules. TCP, DNS, ICMP, and gRPC probes do not use HTTP status codes.
probe_http_duration_seconds{job="blackbox"}
The phase label separates connection, DNS, TLS, processing, and transfer timing where the HTTP probe reports those phases.
A dashboard refresh shorter than the Prometheus scrape interval repeats the same sample and adds browser load without showing fresher probe data.
If a saved panel shows No data, inspect the panel query with the same time range and variable values before changing the data source.
Related: How to troubleshoot a Grafana panel with no data