fix(tracing): Instrument cursors returned from MongoDB operations. #6437
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
onurtemizkan
force-pushed
the
onur/fix-mongodb-tracing-cursors
branch
2 times, most recently
from
128b2ce to
6a821ba
Compare
onurtemizkan
force-pushed
the
onur/fix-mongodb-tracing-cursors
branch
from
6a821ba to
357de02
Compare
AbhiPrasad
approved these changes
Dec 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Checking if the returned value is a
Cursorusing an internal utility instead of matchingEventEmittertype as done in #6412 and #6337.Fixes #4495
Instrumented Cursors returned from certain MongoDB operations, this also resolves the problem mentioned in #5278.