Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support OTel in Transports #3533

Open
iancooper opened this issue Feb 26, 2025 · 1 comment
Open

Support OTel in Transports #3533

iancooper opened this issue Feb 26, 2025 · 1 comment
Labels
0 - Backlog feature request .NET Pull requests that update .net code RC1 v10 Allocal to a v10 release

Comments

@iancooper
Copy link
Member

iancooper commented Feb 26, 2025

Is your feature request related to a problem? Please describe.
We now support clearer OTel throughout Brighter, see here. But the support is only in in-memory transports and needs to be rolled into the middleware transports.

Describe the solution you'd like
We should follow the semantic conventions for messaging. We already have a Span, but we need to write the relevant events to that Span within the transport. See Paramore.Brighter.InMemoryProducer for details.

We don't need this on the Consumer. Following the Semantic Conventions, we only begin a span on the receive.

@iancooper iancooper added .NET Pull requests that update .net code 0 - Backlog feature request v10 Allocal to a v10 release labels Feb 26, 2025
@iancooper
Copy link
Member Author

There is a list of conventions for transports. You will need to determine if the client supports this "out-of-the-box" or if we need to add it, and how we become the parent span (this may be setting Activity.Current)

@iancooper iancooper added the RC1 label Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - Backlog feature request .NET Pull requests that update .net code RC1 v10 Allocal to a v10 release
Projects
None yet
Development

No branches or pull requests

1 participant