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.
Recently, plugin-http was updated to not have pathname in the span name: open-telemetry/opentelemetry-js#1466
It was done with expectation that other plugins like express would add parameterized route in the span name.
Unfortunately, koa plugin doesn't do this so upgrading to the latest opentelemetry version causes traces to be less useful.
Describe the solution you'd like
It would be great if koa plugin can update span name similar to how express does it here: #176
Describe alternatives you've considered
None.
The text was updated successfully, but these errors were encountered:
@akshah123
I’m trying to understand what do you mean by saying It would be great if koa plugin can update span name similar to how express does it here, because this is what I see in some knex / koa postgresql application
@obecny I didn't realize that route gets added as a separate span as well. Initially, HTTP Get span used to have path name as well. I think it should be fine to just have it as is.
Is your feature request related to a problem? Please describe.
Recently, plugin-http was updated to not have pathname in the span name: open-telemetry/opentelemetry-js#1466
It was done with expectation that other plugins like express would add parameterized route in the span name.
Unfortunately, koa plugin doesn't do this so upgrading to the latest opentelemetry version causes traces to be less useful.
Describe the solution you'd like
It would be great if koa plugin can update span name similar to how express does it here: #176
Describe alternatives you've considered
None.
The text was updated successfully, but these errors were encountered: