HttpClient instrumentation sets span name

[DrewJKnowles]

Hello,

I am using the Plugin-Http to export my node traces to Jaeger. When exporting the traces I notice that they are default set to HTTP[method].

Is there a way around to set or configure the naming for the traces that are being exported, Instead of it being HTTP[method] maybe HTTP[method] [pathname}?

opentelemetry-js/packages/opentelemetry-plugin-http/src/http.ts

Line 403 in 24cc9ee

const operationName = `HTTP ${method}`;

Similar to the issue for Dotnet : open-telemetry/opentelemetry-dotnet#1277

[weyert]

Wondering if responseHook would work to override the name of the span? I am having similar wish I will experiment and report back :)

[DrewJKnowles]

I would greatly appreciate if you can let me know on how its possible. I was experimenting but didn't have much luck on using the updateSpan name, it would only change the first spanId but not the children span if I was tracing through multiple method calls.

[vmarchaud]

Is there a way around to set or configure the naming for the traces that are being exported, Instead of it being HTTP[method] maybe HTTP[method] [pathname}?

This was already discuted back in the day, TLDR having path in the name making span low cardinality since they can contains ids (not easily aggregable by backends) so we prefer to avoid this by only using method.

Wondering if responseHook would work to override the name of the span? I am having similar wish I will experiment and report back :)

You can use responseHook and then update the span name with https://github.com/open-telemetry/opentelemetry-js-api/blob/main/src/trace/span.ts#L98

[DrewJKnowles]

Hello, I'm just wondering how I can access the request path?

[dyladan]

The responseHook doesn't receive the request, so it might not be possible to get the path. Technically, it is on the span but not accessible.