HAProxy Enterprise Documentation 2.3r1


The global section appears at the top of your configuration file. It defines process-level directives such as the maximum number of connections to accept, where to forward logs, and the path from which to load HAProxy Enterprise modules.

   # Bind the Runtime API to a UNIX domain socket and/or an IP address
   stats socket /var/run/hapee-2.3/hapee-lb.sock user hapee-lb group hapee mode 660 level admin
   stats socket ipv4@*:9024 level admin

   # Set a timeout for how long you can stay connected to the Runtime API,
   # which is useful for longer interactive terminal sessions
   stats timeout 10m

   # Set remote or local Syslog server addresses to send log files to
   log local0
   log local1 notice

   # Set the user and group to run |hapee| as
   user  hapee-lb
   group hapee

   # Run the process in a chrooted directory
   chroot /var/empty

   # Set the path from which to load Enterprise modules
   module-path /opt/hapee-2.3/modules

Data Plane API

Install the Data Plane API.

You can manage the global section of your configuration remotely by calling the Data Plane API endpoint /services/haproxy/configuration/global.

Get the contents of a global section with the GET method:

$ curl -X GET \
    --user admin:adminpwd \

# output
         "log_send_hostname": { "enabled":"disabled" },

Replace the contents of a global section with the PUT method:

$ curl -X PUT \
    --user admin:adminpwd \
    -H "Content-Type: application/json" \
    -d '{
        "maxconn": 100000,
        "chroot": "/var/empty",
        "user": "hapee-lb",
        "group": "hapee",
        "pidfile": "/var/run/hapee-2.3/hapee-lb.pid",
        "runtime_apis": [{
            "address": "/var/run/hapee-2.3/api.sock",
            "exposeFdListeners": false,
            "level": "admin",
            "mode": "660"
            "address": "ipv4@",
            "exposeFdListeners": false,
            "level": "admin"
    }' \

Next up