Slide 11 of 15

HAProxy integration

HAProxy integration

The HAProxy integration provides load balancer monitoring at every layer: frontend, backend, and individual servers. HAProxy sits in front of your applications and distributes traffic, so when it’s unhealthy, everything behind it suffers.

What it’s forMonitoring traffic distribution, backend health, and capacity
Under the hoodScrapes HAProxy’s built-in Prometheus exporter (HAProxy 2.x and later)

Metrics collected

The integration collects metrics at every layer of the load balancer:

  • Frontend: Connections, requests, bytes
  • Backend: Server count, queue depth, response time
  • Server: Up/down, connections, health checks
  • Sessions: Current, limit, rate

What to know

This integration offers:

  • Prebuilt dashboards: overview, frontend, backend, server
  • Prebuilt alerts: dropped logs, flapping health checks
  • Health check visibility

Set it up

Open this learning path in your Grafana Cloud stack for a fully interactive experience, or read through it to understand the process first.

Learning path

Monitor HAProxy load balancers

Welcome to the Grafana learning path that walks you through monitoring HAProxy load balancers using Grafana Cloud.

14 min
Beginner
Docs & blog posts

Open in Grafana Cloud

Complete this learning path directly in your Grafana Cloud stack with an interactive learning experience.

Path completed

Script

HAProxy sits in front of your applications and distributes traffic, so when it’s unhealthy, everything behind it suffers. The integration gives you visibility at every layer.

Frontend metrics show incoming connections, requests, and throughput. Backend metrics aggregate your server pools with active server counts, queue depths, and response times, while server-level metrics drill into individual backends and health checks, often surfacing failures before users notice.

Setup means enabling HAProxy’s built-in Prometheus exporter, available in HAProxy 2.x and later, which the integration scrapes. For high-traffic sites, queue depths and backend response times make this layer essential for capacity planning.