[EventHubs] Update process span tracing logic #30537
Merged
Conversation
This file contains 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
|
API change check API changes are not detected in this pull request. |
pvaneck
force-pushed
the
eventhub-process-trace
branch
from
a168ad7 to
ef59b65
Compare
In the case of event handling on a per-message basis, the process span should be a direct child of the message context. This change adds the logic to do so. Live tests were also added to test receive/process span tracing. Signed-off-by: Paul Van Eck <[email protected]>
pvaneck
force-pushed
the
eventhub-process-trace
branch
from
ef59b65 to
a8bc075
Compare
|
/azp run python - eventhub - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pvaneck
requested review from
annatisch,
kashifkhan,
swathipil and
l0lawrence
as code owners
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.
In the case of event handling on a per-message basis, the process span should be a direct child of the message context. This change adds the logic to do so.
Additional context: https://gist.github.com/lmolkova/e4215c0f44a49ef824983382762e6b92#processing-messages