We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Open telemetry diagnostic listener fails when Azure service bus is used without a connection string. Azure service bus supports automatic connections when using managed identities, so you don't have to specify connection string. Diagnostic listener has this code that throws a null reference as BrokerAddress.Endpoint is null. https://github.com/dotnetcore/CAP/blob/7ba52a8defa73f3866001dea6dd6af434574c3d2/src/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs#L108C1-L109C1
BrokerAddress.Endpoint
Workaround #1 Explicitly set the connection string for Azure service bus to string empty when registering CAP
The text was updated successfully, but these errors were encountered:
Hi @demorgi ,
Thanks for your report, you're right , would you want to submit a PR to fix it?
Sorry, something went wrong.
Fixed in version 8.0.0
No branches or pull requests
Open telemetry diagnostic listener fails when Azure service bus is used without a connection string.
Azure service bus supports automatic connections when using managed identities, so you don't have to specify connection string. Diagnostic listener has this code that throws a null reference as
BrokerAddress.Endpoint
is null.https://github.com/dotnetcore/CAP/blob/7ba52a8defa73f3866001dea6dd6af434574c3d2/src/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs#L108C1-L109C1
Workaround #1
Explicitly set the connection string for Azure service bus to string empty when registering CAP
The text was updated successfully, but these errors were encountered: