RunTime API allows us to change the settings real-time. Without downtime and restarting-reloading the HAProxy service.
For instance: we want to disable any frontend or backend server. Changes will not to be saved and the all changes will roll back at the next restarting haproxy.
You can checkbox the "Save change" but there is one problem: it won’t to be saved in the config file, what can cause problems with debagging and it will confusing us.
To avoid these problems HAProxy-WI offers you the opportunity use its interface which works with the HAProxy RunTime API. It will edit runtime configuration and saves changes in the config file
Of course here works master-slave behavior which means: if you have made changes on the master server the changes will take effect on the slave server too
Dynamically change the global maxconn setting within the range defined by the
initial global maxconn setting. If it is increased and connections were
pending, they will immediately be accepted. If it is lowered to a value below
the current number of connections, new connections acceptation will be
delayed until the threshold is reached. A value of zero restores the initial
Dynamically change the specified frontend's maxconn setting. Any positive
value is allowed including zero, but setting values larger than the global
maxconn does not make much sense. If the limit is increased and connections
were pending, they will immediately be accepted. If it is lowered to a value
below the current number of connections, new connections acceptation will be
delayed until the threshold is reached.
HAProxy-WI gives ability to change IP and Port for backends on-fly without reloading or restarting HAProxy service.
How it works: first step: we have to choose the server where we want to change settings. second step: choose needs backend,
third step: choose certain server inside the backend (HAProxy-WI shows running settings, you have ablitity to change them), fourth step: press "Enter".
Changes will take effect not only on running configuration, but will be saved in config file too. It means that after restarting HAProxy service they will not be lost.
HTTP requests are stateless by design. However, this raises some questions regarding how to track user activities,
including malicious ones, across requests so that you can collect metrics, block users, and make other decisions
based on state. The only way to track user activities between one request and the next is to add a mechanism for
storing events and categorizing them by client IP or other key.
Out of the box, HAProxy gives you a fast, in-memory storage called stick tables. HAProxy-WI gives you ability to
manage it from GUI.