3b8b9b8179
Depending on the scope, metrics can have different names. For instance, the number of active/backend servers are reported with "haproxy_backend_active_servers"/"haproxy_backend_backup_servers" metric names in the backend scope while it should be "haproxy_server_active"/"haproxy_server_backup" in the server scope. To be able to support different names depending on the scope for the same metric, arrays of ISTs were added, one by scope (front, back, listen, server). These arrays only contain names overriding the default ones. Note: the exemple above is not supported for now and is the reason for this commit.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)