To monitor HAProxy, specify just the unix stats socket path as specified in the global config block. Optionally you can also specify a list of frontend & backends to exclude from monitoring. If unspecified The following default value in data.json will be used.

"haproxy": {
  "socket_address" : "/run/haproxy/admin.sock",
  "exclude_frontend" : [],
  "exclude_backend": []

Having updated data.json on your server (no need to restart archagent), enable this plugin from the server's rule config page. Set thresholds for metrics that you care about and want to be alerted on. Enabling a plugin.

NOTE : This plugin requires the stats reporting to be enabled in HAProxy.

Enabling stats reporting in HAProxy

The default haproxy config is already configured to report metrics via the unix socket at /run/haproxy/admin.sock. If missing, add the line below in the config global block in /etc/haproxy/haproxy.cfg.

stats socket /run/haproxy/admin.sock mode 660 level admin

It is important to ensure that the socket /run/haproxy/admin.sock has read permission for user archsaber. The installer script has been configured to do that, and it adds user archsaber to the haproxy group. However, in case Haproxy has been installed as a different user, please add to that group manually by running the following command.

sudo usermod -a -G <haproxy-group>,archsaber archsaber

The stats reporting can be tested by running the below command on the haproxy instance (socat package is required).

echo "show info" | socat unix-connect:/run/haproxy/admin.sock stdio

results matching ""

    No results matching ""