Skip to content

Enable Tracing for RabbitMQ Component when we move to their v7 #562

@eerhardt

Description

@eerhardt

Once we have a build of RabbitMQ.Client with rabbitmq/rabbitmq-dotnet-client#1261, we will need to enable and document the "RabbitMQ.Client" ActivitySource for our component.

One thing to note is that we added our own ActivitySource for the connection retries we do:

private const string ActivitySourceName = "Aspire.RabbitMQ.Client";
private static readonly ActivitySource s_activitySource = new ActivitySource(ActivitySourceName);

We should think about how to rectify the 2 activity sources in the future. One possibility is that once open-telemetry/semantic-conventions#454 is completed, we might not need our own ActivitySource for tracing the connection tries.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-integrationsIssues pertaining to Aspire Integrations packagesblockedexternalIssues that represent work that's external to this repo.rabbitmqIssues related to rabbitmq integrations

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions