NodeJS: update mongodb instrumentation version to 0.59.0
#1982
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rndD
force-pushed
the
alex-k_mongodb-update
branch
from
d7097bd to
2d05ce4
Compare
Contributor
|
Thank you for informing us, this has been updated through dependabot pr #1983 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There was an issue with the default
dbStatementSerializerblocking us from using MongoDB instrumentation in lambdas. Since there is no way to set the serializer, we locked with the default one in the lambda OTEL layer.It was fixed in open-telemetry/opentelemetry-js-contrib#3131 and released in https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mongodb-v0.59.0.