A Prometheus exporter that scrapes HAProxy statistics and exposes them as metrics for monitoring.
HAProxy Exporter is a monitoring agent that scrapes statistics from HAProxy load balancers and exposes them as Prometheus metrics. It solves the problem of integrating HAProxy performance data into a Prometheus-based observability stack, allowing operators to track request rates, error counts, backend health, and queue states. The exporter acts as a bridge, converting HAProxy's native CSV stats format into the time-series data model Prometheus understands.
DevOps engineers, SREs, and system administrators who manage HAProxy load balancers and use Prometheus for monitoring their infrastructure.
Developers choose this exporter because it provides a standardized, reliable way to monitor HAProxy with Prometheus before native exporter support was available. It offers flexible configuration for different HAProxy deployments (including authentication and proxy support) and follows the well-established Prometheus exporter design pattern.
Simple server that scrapes HAProxy stats and exports them via HTTP for Prometheus consumption
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports HTTP, HTTPS, and Unix sockets for HAProxy stats, allowing adaptation to diverse setups like remote servers or local sockets as detailed in the README.
Provides basic authentication and TLS with options to hide passwords from process tables, enhancing security for production use as shown in the flag examples.
Can route requests through HTTP proxies using standard environment variables (e.g., $HTTP_PROXY), useful in corporate networks as enabled by the --http.proxy-from-env flag.
Available as a Docker container from Quay.io, simplifying deployment in containerized environments without manual builds.
The README explicitly states this exporter is retired in favor of HAProxy's native Prometheus exporter, meaning no updates or bug fixes will be provided.
Requires running a separate service with complex flag-based configuration (e.g., --haproxy.scrape-uri), increasing maintenance compared to the integrated solution.
Lacks features from HAProxy's native exporter, such as direct configuration via haproxy.cfg, making it less optimal for current deployments.