Skip to main content

Blackbox exporter (blackbox-exporter)

Probes HTTP, TCP and TLS endpoints and reports availability, latency and certificate expiry.

Generated from catalog/services/blackbox-exporter.yaml: do not edit by hand.

Summary​

Version0.27.0
Useinstall and configure
Layerinfrastructure (shown apart)
CategoryObservability
Installation methodsbinary
External connectionno
Sandbox onlyno

Licence​

SPDX identifierApache-2.0
Licence policycore licence (MIT or Apache-2.0)
Licence exception-
Platform componentblackbox-exporter

Packages and artifacts​

A package the project of the service publishes (its image, its binary archive, its Python or OS package) carries the licence of the service; a third-party package carries the licence written on its row, read from the official upstream metadata.

KindPackageVersionLicenceDetails
binary archiveblackbox_exporter-0.27.0.linux-amd64.tar.gz0.27.0Apache-2.0https://github.com/prometheus/blackbox_exporter/releases/download/v0.27.0/blackbox_exporter-0.27.0.linux-amd64.tar.gz, x86_64, checksum sha256

Supported systems and architectures​

MethodOperating systemsArchitectures
binaryRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64 (architecture of the artifacts of the descriptor)

Certified host systems: RHEL 8/9/10, Rocky Linux 8/9/10, AlmaLinux 8/9/10, Oracle Linux 8/9, CentOS Stream 9/10, Ubuntu 22.04/24.04, Debian 12, Arch Linux (rolling). The host preflight accepts these systems (other releases of a known family give a warning, end of life releases are refused) and the x86_64 and aarch64 architectures.

Prerequisites​

Host​

The descriptor declares no host preflight check.

Programs the commands and checks of the service start on the host, outside the managed roots: add them to allowed_commands of the agent (see Security of the Navin agent), else the agent refuses them with command_not_allowed: /usr/bin/curl.

Network and ports​

ComponentPort namePortOpened in the host firewall
blackbox-exporterhttp9115/tcpyes

Services and connections needed​

This service has no dependency.

Installation methods and modes​

MethodDefaultWhat the method uses
binaryyesthe binary archives of the descriptor, unpacked under the service directory

Components​

ComponentKindInstallation methodsPorts
Blackbox exporter (blackbox-exporter)workerbinary9115/tcp

Single (single) (default)​

One prober.

What the mode deploys:

ComponentPlacement
blackbox-exportermin 1, recommended 1

Install this service​

The install wizard of the Navin Manager plans, validates and runs the installation; you need the services:install permission on the cluster.

  1. Open the wizard. In Clusters, choose the row action Install services of the target cluster. The wizard opens on its first step, Service.

  2. Choose the service. On the Service step, select Blackbox exporter. The card shows the licence Apache-2.0.

  3. Choose the hosts and the mode. On the Hosts step, tick the hosts, then choose the Mode: single (default). Each mode deploys the components listed in Installation methods and modes.

  4. Bindings. This service has no dependency: the Bindings step has nothing to bind.

  5. Configure. On the Configure step, review the parameters (see Configuration parameters). Passwords left empty with a generated default are generated and sealed by the Manager.

  6. Review and install. On the Install step the Manager validates the plan and shows the installation order; when it says "The plan is valid. Ready to install.", choose Install. A highly available mode is installed only when its HA checks pass.

  7. Verify. The operation ends when the health checks of every instance pass (see Health checks); the service then shows as running in Services.

High availability​

Clusternone (none)
High availabilityredundancy (redundancy)
Failovernone (none)
Replicationnone (none)
Quorumnone (none)
Discoverystatic (static)
Entry pointany node (any-node)
Official documentationhttps://github.com/prometheus/blackbox_exporter/blob/master/README.md

Topology per mode​

ModesHighest catalog levelDistributionQuorum componentFault domainsDescription
singlestandalone (standalone)single (single)-1One prober; install it on several hosts for independent redundant probes.

Notes​

  • Redundancy only: each prober is independent and Prometheus scrapes each one; there is no shared state and no failover.

Configuration parameters​

General​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
HTTP port (port)port9115-nononoPort of /probe and /metrics.
TLS (tls_enabled)boolfalse-nononoServe /probe, /metrics and /-/reload over HTTPS (--web.config.file) with a certificate issued by the manager CA; Prometheus then scrapes it in https and verifies it with that CA.
Probes (probes)json[]-nononoList of {name, module, target}; module is http_2xx, tcp_connect or tls_connect. The manager health probe is always added. Prometheus runs the probes through its blackbox binding (job navin-probes).

Endpoints​

EndpointSchemeComponentPortPathTLS parameterBinding parametersBinding secretsProvisioning command
httphttpblackbox-exporter9115 (port)-tls_enabledprobe_targets--

Commands​

CommandComponentTargetDescription
Reload (reload)blackbox-exporterevery hostReloads the modules without restart.

Health checks​

Liveness (per instance)​

ComponentCheckDetails
blackbox-exporterHTTP {{ 'https' if config.tls_enabled else 'http' }}://{{ host.fqdn if config.tls_enabled else (host.ip or '127.0.0.1') }}:{{ config.port }}/-/healthyExpected 200; 20 retries; interval 1 s; timeout 3 s

Preflight checks​

CheckTypeMeaningSeverityComponents
port_freeport_free {"param": "port"}port 9115 free on the hostblockingevery component

Uninstall​

Paths removed when the data is purged: {{ paths.log }}.

Upstream documentation​