feat(node): Expose getHttpInstrumentationOptions
utility
#13719
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to getsentry/sentry-docs#11378
It can be a bit tricky/annoying for users with a custom otel setup to understand that they cannot add their own
HttpInstrumentation
, because this will overwrite ours which we need.This PR exposes a new utility,
getHttpInstrumentationOptions()
, which can be used to define your own HttpInstrumentation:this way it does not matter that/if that overwrites the instrumentation we added in the first place, http instrumentation will still work as expected then.