and Zipkin.
Note: The OpenTracing filter shouldn't be used for new designs as OpenTracing
- itself is no longer maintained nor supported by its authors. A
- replacement filter base on OpenTelemetry is currently under development
- and is expected to be ready around HAProxy 3.2. As such OpenTracing will
- be deprecated in 3.3 and removed in 3.5.
+ itself is no longer maintained nor supported by its authors. As such
+ OpenTracing will be deprecated in 3.3 and removed in 3.5. A replacement
+ filter based on OpenTelemetry is available since 3.4 with complete build
+ instructions currently at:
-The OT filter was primarily tested with the Jaeger tracer, while configurations
-for both Datadog and Zipkin tracers were also set in the test directory.
+ https://github.com/haproxytech/haproxy-opentelemetry/
The OT filter is a standard HAProxy filter, so what applies to others also
applies to this one (of course, by that I mean what is described in the
of the filter can be found in the addons/ot directory.
Note: The OpenTracing filter shouldn't be used for new designs as OpenTracing
- itself is no longer maintained nor supported by its authors. A
- replacement filter base on OpenTelemetry is currently under development
- and is expected to be ready around HAProxy 3.2. As such OpenTracing will
- be deprecated in 3.3 and removed in 3.5.
+ itself is no longer maintained nor supported by its authors. As such
+ OpenTracing will be deprecated in 3.3 and removed in 3.5. A replacement
+ filter based on OpenTelemetry is available since 3.4 with complete build
+ instructions currently at:
+
+ https://github.com/haproxytech/haproxy-opentelemetry/
9.7. Bandwidth limitation