Skip to content

[Azure.Messaging.EventGrid.Namespaces] Add trace context to distributed tracing#49485

Merged
m-redding merged 10 commits intoAzure:mainfrom
m-redding:oteleventgrid
Apr 22, 2025
Merged

[Azure.Messaging.EventGrid.Namespaces] Add trace context to distributed tracing#49485
m-redding merged 10 commits intoAzure:mainfrom
m-redding:oteleventgrid

Conversation

@m-redding
Copy link
Copy Markdown
Member

@m-redding m-redding commented Apr 18, 2025

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.

@azure-sdk
Copy link
Copy Markdown
Collaborator

API change check

API changes are not detected in this pull request.

@m-redding
Copy link
Copy Markdown
Member Author

/azp run net - eventgrid - tests

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@m-redding
Copy link
Copy Markdown
Member Author

/azp run net - eventgrid - tests

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@m-redding
Copy link
Copy Markdown
Member Author

/azp run net - eventgrid - tests

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@m-redding m-redding marked this pull request as ready for review April 22, 2025 20:36
@m-redding m-redding merged commit cb55185 into Azure:main Apr 22, 2025
32 checks passed
@m-redding m-redding deleted the oteleventgrid branch April 22, 2025 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Azure.Messaging.EventGrid.Namespaces does not work with distributed tracing while Azure.Messaging.EventGrid does

4 participants