Blackbox Exporter: Network endpoint monitoring tool
Prometheus exporter for blackbox probing of network endpoints over HTTP, TCP, DNS, ICMP, and gRPC protocols.
Learn more about Blackbox Exporter
Blackbox Exporter is a Prometheus exporter that performs external monitoring of network services and endpoints. It works by probing targets over various protocols including HTTP, HTTPS, DNS, TCP, ICMP, and gRPC, then exposing the results as Prometheus metrics. The exporter runs as a standalone service that accepts probe requests via HTTP API calls, with configurable modules defining different probe types and parameters. It is commonly used for uptime monitoring, SLA measurement, and network connectivity testing in observability stacks.
Multi-Protocol Support
Supports probing across six different protocols (HTTP, HTTPS, DNS, TCP, ICMP, gRPC) from a single exporter instance. Each protocol probe can be configured with specific parameters and validation rules.
External Perspective
Performs blackbox monitoring from outside the target system, providing visibility into service availability as experienced by external users. This complements internal monitoring by detecting issues that may not be visible from within the infrastructure.
Configurable Modules
Uses a flexible module system where different probe configurations can be defined and reused across multiple targets. Modules can specify timeouts, expected response codes, TLS settings, and other protocol-specific parameters.
Introduces HTTP/3 support, improves logging with breaking changes, and adds automatic configuration reloading with gRPC metadata support.
- –The --log.prober flag behavior has changed. The scrape probe logger is now an independent logger
- –Make default HTTP User-Agent compliant with RFC9110
- –Config is not reloaded if the file content didn't change when using all reload methods
- –Support HTTP/3 (QUIC) prober
- –Add support for configuring gRPC metadata in gRPC prober
This release adds JSON body matching with CEL expressions and fixes DNS lookup conditions and logging issues.
- –Support matching JSON body with CEL expressions
- –Fix condition when local dns lookup should happen
- –Stop scrape logger spam
Introduces new TLS metrics, certificate serial number reporting, and switches to the standard log/slog package with various enhancements.
- –adopt log/slog, drop go-kit/log
- –Add metric to record tls ciphersuite negotiated during handshake
- –Add a way to export labels with content matched by the probe
- –Reports Certificate Serial number
- –Enable misspell linter
Related Repositories
Discover similar tools and frameworks used by developers
Azure CLI
Cross-platform CLI for managing Azure resources through commands and automation scripts.
Temporal
Distributed system for durable workflow execution with automatic failure handling, retries, and state persistence.
OpenLens
Community-built Kubernetes IDE without authentication requirements.
Podman
Daemonless OCI container management with Docker-compatible CLI and rootless execution support.
Setup Node
Node.js version management and dependency caching for workflows.
Related Reading
Guides and comparisons from the Greptile content library
Best Security-Focused AI Code Review Tools [2026 Guide]
The six best security-focused AI code review tools, compared on SAST, SCA, DAST, and full-repo context, so you can pick the one that fits your codebase and your cycle times.
Automated Code Review: How It Works & Best Tools [2026]
What automated code review is, how it differs from traditional and AI code review, the six types of code review automation tools, and why linters and SAST alone are no longer enough as agentic coding grows.
What is a pull request & why is it important for code reviews?
Pull requests protect your codebase, but traditional PR workflows are becoming the bottleneck as AI writes more code. Learn what pull requests are, how to create one, and how to automate PR review so velocity and trust scale together.
Flaky Tests: What Is a Flaky Test and How Do You Manage Them?
What flaky tests are, what causes them, how to detect them, and 12 ways to fix them. Plus why end-to-end tests are more prone to flakiness, and how seeing what actually happened during a run helps you tell a test problem from a code problem.