Implement tracing in AMQP client libraries supported by the RabbitMQ team

[lukebakken]

Is your feature request related to a problem? Please describe.

Currently there is no coordinated way to trace RabbitMQ applications using a solution like OpenTelemetry.

Describe the solution you'd like

@ikvmw is taking lead on ensuring that our top client libraries (Java, .NET, Go and Python) use compatible OpenTelemetry tracing configurations.

Describe alternatives you've considered

No response

Additional context

• https://github.com/rabbitmq/contribute/blob/main/observability/clients.md
• Add OpenTelemetry support via ActivitySource rabbitmq-dotnet-client#1261
• Support Micrometer observation rabbitmq-java-client#1017
• Feature Proposal: W3C Context propagation integration via OpenTelemetry amqp091-go#43

[ikavgo]

Thanks Luke !

I added a Golang client. I had a chat with @HowardTwine about client libraries priorities. I pointed out that it might be that Golang community much eager to use our new OT support. While I don't know our language distribution, I judge by myself :-). For me this real opensource, opencommunity Observability started with Google folks and Prometheus which continues now with Loki, etc. I'm well aware we had observability before Prometheus :-). But I have a feeling that just like kubernetes, Google folks exported this openness to the world which engraved itself in the golang community. Again example from my own life - knative has tracing builting :-) and written in go.

While calculating our priorities for clients, as well as other material like tutorials, I'd like to suggest taking into account this Observability adoption perceived rate.