3184470339
Connected the OpenTelemetry C wrapper library to the filter lifecycle by implementing the library initialization, tracer creation, memory and thread callbacks, shutdown sequence, and span completion. The flt_otel_lib_init() function now verifies the C wrapper library version against the compiled headers, calls otelc_init() with the absolute configuration file path, and creates the tracer via otelc_tracer_create(). On success, it registers HAProxy pool-based memory callbacks (flt_otel_mem_malloc, flt_otel_mem_free) and a thread ID callback (flt_otel_thread_id) through otelc_ext_init(), so the C++ SDK allocates span and context objects from pool_head_otel_span_context. A custom log handler (flt_otel_log_handler_cb) is registered via otelc_log_set_handler() to count OTel SDK internal diagnostic messages in the flt_otel_drop_cnt counter. The per-thread init callback now starts the tracer thread via OTELC_OPS(tracer, start) instead of unconditionally returning success. The deinit callback saves the tracer handle before freeing the configuration, then shuts down the library via otelc_deinit() after the pool is destroyed, ensuring the ext callbacks remain valid while the configuration structures are still being freed. In debug builds, it logs wrapper statistics, attach counters, and per-event HTX usage counters before shutdown. The runtime context cleanup in flt_otel_runtime_context_free() now ends all active spans with a common monotonic timestamp via OTELC_OPSR(span, end_with_options) before freeing them. The scope context cleanup in flt_otel_scope_context_free() now destroys the underlying OTel span context via OTELC_OPSR(context, destroy). The parser gained static storage for the debug memory tracker (OTELC_DBG_MEM) and its initialization in the parse entry point, used when compiled with the OTELC_DBG_MEM flag.
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.