HAProxy OpenTelemetry Assets

HAProxy is a high-performance TCP/HTTP load balancer and reverse proxy that distributes traffic across backend servers. This content pack provides dashboards, alert rules, and SLO templates for monitoring HAProxy via the OpenTelemetry HAProxy receiver, covering traffic, latency, errors, saturation, and backend availability.

The HAProxy OpenTelemetry assets have been tested with:

• OpenTelemetry haproxyreceiver v0.144.0 from OpenTelemetry Collector Contrib.
• HAProxy 3.x

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

Enable the HAProxy stats interface so the collector can poll metrics. Add a listen or frontend block to your HAProxy configuration:

listen stats
    bind *:8404
    stats enable
    stats uri /stats
    stats refresh 10s
    # Optional: stats auth <user>:<password>

For Unix socket access instead of HTTP:

listen stats
    bind *:8404
    stats enable
    stats socket /var/run/haproxy.sock mode 660 level admin

Verify the stats endpoint. For HTTP: curl -s "http://localhost:8404/stats;csv". For socket: echo "show stat" | socat stdio /var/run/haproxy.sock.

Configure the OpenTelemetry Collector or Elastic Observability Distribution (EDOT) Collector to receive HAProxy metrics and export them to Elasticsearch. The following example wires the haproxy receiver to the elasticsearch/otel exporter.

receivers:
  haproxy:
    endpoint: <HAPROXY_ENDPOINT>
    collection_interval: 1m
    metrics:
      haproxy.active:
        enabled: true
      haproxy.sessions.limit:
        enabled: true
      haproxy.connections.average_time:
        enabled: true
      haproxy.requests.average_time:
        enabled: true
      haproxy.responses.average_time:
        enabled: true
      haproxy.failed_checks:
        enabled: true

exporters:
  elasticsearch/otel:
    endpoints: [<ES_ENDPOINT>]
    api_key: <ES_API_KEY>
    mapping:
      mode: otel

service:
  pipelines:
    metrics:
      receivers: [haproxy]
      exporters: [elasticsearch/otel]

1. disabled by default — required for Backend availability SLO and alerts
2. disabled by default — required for Session saturation alert
3. disabled by default — required for High connection time alert
4. disabled by default — required for High queue time alert
5. disabled by default — required for Response time SLO and High response time alert
6. disabled by default — required for Health check failures alert

Refer to the metadata.yaml of the OpenTelemetry HAProxy receiver for details on available metrics.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.