CONTRIB: opentracing: add the OpenTracing filter
This commit adds the OpenTracing filter (hereinafter we will use the
abbreviated name 'the OT filter') to the contrib tree.
The OT filter adds native support for using distributed tracing in HAProxy.
This is enabled by sending an OpenTracing compliant request to one of the
supported tracers; such as Datadog, Jaeger, Lightstep and Zipkin tracers.
Please note: tracers are not listed by any preference, but alphabetically.
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
documentation, more precisely in the doc/internals/filters.txt file).
The OT filter activation is done explicitly by specifying it in the HAProxy
configuration. If this is not done, the OT filter in no way participates
in the work of HAProxy.
As for the impact on HAProxy speed, this is documented with several tests
located in the test directory, and the result is found in the README-speed-*
files. In short, the speed of operation depends on the way it is used and
the complexity of the configuration, from an almost immeasurable impact to
a significant deceleration (5x and more). I think that in some normal use
the speed of HAProxy with the filter on will be quite satisfactory with a
slowdown of less than 4%.
The OT filter allows intensive use of ACLs, which can be defined anywhere in
the configuration. Thus, it is possible to use the filter only for those
connections that are of interest to us.
More detailed documentation related to the operation, configuration and use
of the filter can be found in the contrib/opentracing directory.
To make the OpenTracing filter easier to configure and compile, several
entries have been added to the Makefile. When running the make utility,
it is possible to use several new arguments:
USE_OT=1 : enable the OpenTracing filter
OT_DEBUG=1 : compile the OpenTracing filter in debug mode
OT_INC=path : force the include path to libopentracing-c-wrapper
OT_LIB=path : force the lib path to libopentracing-c-wrapper
OT_RUNPATH=1 : add libopentracing-c-wrapper RUNPATH to haproxy executable
If USE_OT is set, then an additional Makefile from the contrib/opentracing
directory is included in the compilation process.
2020-12-09 15:54:31 +00:00
|
|
|
[ot-test-cmp]
|
|
|
|
|
ot-tracer ot-test-tracer
|
|
|
|
|
config cmp/cfg-jaeger.yml
|
|
|
|
|
plugin libjaeger_opentracing_plugin-0.5.0.so
|
|
|
|
|
# log localhost:514 local7 debug
|
|
|
|
|
option dontlog-normal
|
|
|
|
|
option hard-errors
|
|
|
|
|
no option disabled
|
|
|
|
|
rate-limit 100.0
|
|
|
|
|
|
|
|
|
|
scopes client_session_start
|
|
|
|
|
scopes frontend_tcp_request
|
|
|
|
|
scopes frontend_http_request
|
|
|
|
|
scopes backend_tcp_request
|
|
|
|
|
scopes backend_http_request
|
|
|
|
|
scopes server_unavailable
|
|
|
|
|
|
|
|
|
|
scopes server_session_start
|
|
|
|
|
scopes tcp_response
|
|
|
|
|
scopes http_response http_response-error server_session_end client_session_end
|
|
|
|
|
|
|
|
|
|
ot-scope client_session_start
|
|
|
|
|
span "HAProxy session" root
|
2022-02-23 09:28:10 +00:00
|
|
|
baggage "haproxy_id" var(sess.ot.uuid)
|
CONTRIB: opentracing: add the OpenTracing filter
This commit adds the OpenTracing filter (hereinafter we will use the
abbreviated name 'the OT filter') to the contrib tree.
The OT filter adds native support for using distributed tracing in HAProxy.
This is enabled by sending an OpenTracing compliant request to one of the
supported tracers; such as Datadog, Jaeger, Lightstep and Zipkin tracers.
Please note: tracers are not listed by any preference, but alphabetically.
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
documentation, more precisely in the doc/internals/filters.txt file).
The OT filter activation is done explicitly by specifying it in the HAProxy
configuration. If this is not done, the OT filter in no way participates
in the work of HAProxy.
As for the impact on HAProxy speed, this is documented with several tests
located in the test directory, and the result is found in the README-speed-*
files. In short, the speed of operation depends on the way it is used and
the complexity of the configuration, from an almost immeasurable impact to
a significant deceleration (5x and more). I think that in some normal use
the speed of HAProxy with the filter on will be quite satisfactory with a
slowdown of less than 4%.
The OT filter allows intensive use of ACLs, which can be defined anywhere in
the configuration. Thus, it is possible to use the filter only for those
connections that are of interest to us.
More detailed documentation related to the operation, configuration and use
of the filter can be found in the contrib/opentracing directory.
To make the OpenTracing filter easier to configure and compile, several
entries have been added to the Makefile. When running the make utility,
it is possible to use several new arguments:
USE_OT=1 : enable the OpenTracing filter
OT_DEBUG=1 : compile the OpenTracing filter in debug mode
OT_INC=path : force the include path to libopentracing-c-wrapper
OT_LIB=path : force the lib path to libopentracing-c-wrapper
OT_RUNPATH=1 : add libopentracing-c-wrapper RUNPATH to haproxy executable
If USE_OT is set, then an additional Makefile from the contrib/opentracing
directory is included in the compilation process.
2020-12-09 15:54:31 +00:00
|
|
|
span "Client session" child-of "HAProxy session"
|
|
|
|
|
event on-client-session-start
|
|
|
|
|
|
|
|
|
|
ot-scope frontend_tcp_request
|
|
|
|
|
span "Frontend TCP request" child-of "Client session"
|
|
|
|
|
event on-frontend-tcp-request
|
|
|
|
|
|
|
|
|
|
ot-scope frontend_http_request
|
|
|
|
|
span "Frontend HTTP request" follows-from "Frontend TCP request"
|
|
|
|
|
tag "http.method" method
|
|
|
|
|
tag "http.url" url
|
|
|
|
|
tag "http.version" str("HTTP/") req.ver
|
|
|
|
|
finish "Frontend TCP request"
|
|
|
|
|
event on-frontend-http-request
|
|
|
|
|
|
|
|
|
|
ot-scope backend_tcp_request
|
|
|
|
|
span "Backend TCP request" follows-from "Frontend HTTP request"
|
|
|
|
|
finish "Frontend HTTP request"
|
|
|
|
|
event on-backend-tcp-request
|
|
|
|
|
|
|
|
|
|
ot-scope backend_http_request
|
|
|
|
|
span "Backend HTTP request" follows-from "Backend TCP request"
|
|
|
|
|
finish "Backend TCP request"
|
|
|
|
|
event on-backend-http-request
|
|
|
|
|
|
|
|
|
|
ot-scope server_unavailable
|
|
|
|
|
span "HAProxy session"
|
|
|
|
|
tag "error" bool(true)
|
|
|
|
|
log "status" str("503 Service Unavailable")
|
|
|
|
|
finish *
|
|
|
|
|
event on-server-unavailable
|
|
|
|
|
|
|
|
|
|
ot-scope server_session_start
|
|
|
|
|
span "Server session" child-of "HAProxy session"
|
|
|
|
|
finish "Backend HTTP request"
|
|
|
|
|
event on-server-session-start
|
|
|
|
|
|
|
|
|
|
ot-scope tcp_response
|
|
|
|
|
span "TCP response" child-of "Server session"
|
|
|
|
|
event on-tcp-response
|
|
|
|
|
|
|
|
|
|
ot-scope http_response
|
|
|
|
|
span "HTTP response" follows-from "TCP response"
|
|
|
|
|
tag "http.status_code" status
|
|
|
|
|
finish "TCP response"
|
|
|
|
|
event on-http-response
|
|
|
|
|
|
|
|
|
|
ot-scope http_response-error
|
|
|
|
|
span "HTTP response"
|
|
|
|
|
tag "error" bool(true)
|
|
|
|
|
event on-http-response if !acl-http-status-ok
|
|
|
|
|
|
|
|
|
|
ot-scope server_session_end
|
|
|
|
|
finish "HTTP response" "Server session"
|
|
|
|
|
event on-http-response
|
|
|
|
|
|
|
|
|
|
ot-scope client_session_end
|
|
|
|
|
finish "*"
|
|
|
|
|
event on-http-response
|