[Azure.Messaging.EventGrid.Namespaces] Add trace context to distributed tracing #49485
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
|
API change check API changes are not detected in this pull request. |
m-redding
force-pushed
the
oteleventgrid
branch
from
9848134 to
3bbd297
Compare
|
/azp run net - eventgrid - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - eventgrid - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run net - eventgrid - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
jsquire
approved these changes
Apr 22, 2025
JoshLove-msft
approved these changes
Apr 22, 2025
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.
Fixes: #49341
Related:
I also explored an alternative implementation of creating an internal pipeline policy as suggested by the issue linked above. Other languages do that and manipulate the serialized http message body. Since the message body is BinaryData it's pretty hard to do this in .NET so just following the same implementation as Azure.Messaging.EventGrid.