Skip to content

Conversation

@pichlermarc
Copy link
Member

Which problem is this PR solving?

Context managers were not properly registered when no trace-releated options were passed to the NodeSDK constructor.

Fixes #4776

Short description of the changes

Falls back to the raw contextManager option in case the tracer options are undefined.

Type of change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

  • Added Unit test

@pichlermarc pichlermarc requested a review from a team June 10, 2024 10:59
@pichlermarc pichlermarc added this pull request to the merge queue Jun 11, 2024
Merged via the queue into open-telemetry:main with commit 05e2699 Jun 11, 2024
@pichlermarc pichlermarc deleted the fix/4776-context-manager-not-registered branch June 11, 2024 07:26
Zirak pushed a commit to Zirak/opentelemetry-js that referenced this pull request Sep 14, 2024
…ided (open-telemetry#4781)

* fix(sdk-node): register context manager if no tracer options are provided

* chore: add changelog entry
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Custom context manager not respected when span processors / exporters are configured via env vars

3 participants