Ship `RabbitMQ.Client.OpenTelemetry` `1.0.0`

[lukebakken]

https://www.nuget.org/packages/RabbitMQ.Client.OpenTelemetry/

[lukebakken]

https://opentelemetry.io/docs/specs/semconv/messaging/messaging-spans/

[BOLT04]

Hello everyone,
Does anyone know the status of this issue and the whole milestone? There is only this issue on the milestone, so I'm not sure what is missing from the messaging conventions.

v7.0.0 released recently and it included some PRs for OpenTelemetry, which is awesome!

I saw recent changes related to OpenTelemetry conventions #1717 , @lukebakken is there a task list or backlog of some kind for us to know when RabbitMQ.Client.OpenTelemetry 1.0.0 is ready to ship?

Thanks in advance 🙂!

[lukebakken]

I'm extremely busy working for customers who pay Broadcom for RabbitMQ support. I am also working on higher-priority issues, such as #1750.

What would help me out is for someone, like you, to build this project from source and ensure that the OTel changes that have been made in main work as intended, and make sense. I don't know much about OTel so I'm relying on community members to provide input, reviews, and do testing.

[codedesignplus-wliscano]

Hello everyone,
I want to share with you how the RabbitMQ.Client.OpenTelemetry library works. In this context, I have a microservice that manages users and replicates the domain event with Rabbit to the Microsoft Graph and Email microservice. These microservices report to the OTEL Collector, which I have deployed in the cluster, and it then sends the information to Grafana Cloud.

1. The image of the OTEL Collector in Kubernetes.

2. When making update requests to the user, the interaction with RabbitMQ is evident.

3. By viewing the details of the trace, the Spans containing RabbitMQ information can be seen.

4. We can also see the service map (infrastructure) that the microservice interacts with.