Closed derekkraan closed 1 month ago
Continuing from a discussion I had on Slack with @bryannaegele.
This pertains to the behaviour present in the OpentelemetryReq library, where the request can be halted under the following circumstances:
:no_path_params
path_params
Req.Request
The main issue from my point of view is that the instrumentation is changing application behaviour by halting the request here.
Describe the solution you'd like
no_path_params: true
HTTP GET /foo/:bar
HTTP GET
info
debug
Describe alternatives you've considered None
Additional context None
Continuing from a discussion I had on Slack with @bryannaegele.
This pertains to the behaviour present in the OpentelemetryReq library, where the request can be halted under the following circumstances:
:no_path_params
option is unsetpath_params
has not been used in theReq.Request
The main issue from my point of view is that the instrumentation is changing application behaviour by halting the request here.
Describe the solution you'd like
:no_path_params
option in favour of the branchno_path_params: true
.HTTP GET /foo/:bar
to simplyHTTP GET
info
, I'd suggestdebug
) when this fallback occurs.Describe alternatives you've considered None
Additional context None