Align capabilities of `nativeNodeFetchIntegration` with `httpIntegration`

[lforst]

Problem Statement

The http integration has powerful hooks to augment spans with attributes based on req and res. Would be great to have the same thing for the native node fetch integration.

Solution Brainstorm

Thinking instrumentation.applyCustomAttributesOnSpan would be a cool candidate to move over.

Additional Context

No response

[linear]

JS-1058

[JPeer264]

Hey, nice to see you again ;) May I ask you what you want to achieve?

The reason why I ask is that underneath we are using OTels undici instrumentation, which differs a little from the OTels HTTP instrumentation which also means that there is no applyCustomAttributesOnSpan there.

The implementation of http and undici varies a little. It seems, also based on open-telemetry/opentelemetry-js-contrib#2265, that the responseHook from the undici instrumentation is almost the same. Do you think that hook would solve your issue?

[lforst]

May I ask you what you want to achieve?

For example taking response headers and writing their values to attributes.

Do you think open-telemetry/opentelemetry-js-contrib#2265 (comment) would solve your issue?

Yup that would probably work.