mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-02-11 20:31:11 +01:00
12ae212837
For now the traces are not used. Supported events are categorized by where the activity comes from (h2c, h2s, stream, etc), a direction (send/recv/wake), and a list of possibilities for each of them (frame types, errors, shut, ...). This results in ~50 different events that try to cover a lot of possibilities when it's needed to filter on something specific. Special events like protocol error are handled. A few aggregate events like "rx_frame" or "tx_frame" are planed to cover all frame types at once by being placed all the time with any of the other ones. We also state that the first argument is always the connection. This way the trace subsystem will be able to safely retrieve some useful info, and we'll still be able to get the h2c from there (conn->ctx) in a pretty print function. The second argument will always be an h2s, and in order to propose it for tracking, we add its description. We also define 4 verbosity levels, which seems more than enough.
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)