You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
Currently the root span name is set by the http instrumentation to a generic name like HTTP GET. Additionally, http.route of the root span is set to the actual http pathname and not the route. So, something like http.route: /events/123 instead of http.route: /events/{eventId}.
This makes traces hard to identify (in Honeycomb in this case):
The actual hapi route is buried somewhat deep in the trace:
Describe the solution you'd like to see
Similarly to the way it's done for Koa (#327) and Express (#176, #273) the root span name should be renamed once the route has been determined and http.route should be set to the actual route at that point.
Describe alternatives you've considered
None
Thank you for your work on OpenTelemetry and all these instrumentations :)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
Currently the root span name is set by the http instrumentation to a generic name like
HTTP GET
. Additionally,http.route
of the root span is set to the actual http pathname and not the route. So, something likehttp.route: /events/123
instead ofhttp.route: /events/{eventId}
.This makes traces hard to identify (in Honeycomb in this case):
The actual hapi route is buried somewhat deep in the trace:
Describe the solution you'd like to see
Similarly to the way it's done for Koa (#327) and Express (#176, #273) the root span name should be renamed once the route has been determined and
http.route
should be set to the actualroute
at that point.Describe alternatives you've considered
None
Thank you for your work on OpenTelemetry and all these instrumentations :)
The text was updated successfully, but these errors were encountered: