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

Azure ServiceBus instrumentation causing recursion errors. #2313

Open
sluebbert opened this issue Mar 21, 2024 · 0 comments
Open

Azure ServiceBus instrumentation causing recursion errors. #2313

sluebbert opened this issue Mar 21, 2024 · 0 comments
Labels

Comments

@sluebbert
Copy link

APM Agent version

1.26.0 and earlier versions.

Environment

Operating system and version:
Windows 11 and Linux

.NET Framework/Core name and version (e.g. .NET 4.6.2, NET Core 3.1.100) :
.net 8.0

Application Target Framework(s) (e.g. net462, netcoreapp3.1):
net8.0

Describe the bug

The Azure ServiceBus instrumentation appears to be causing recursion issues in Kibana when displaying spans for a sent message.

The closest related issue I could find for this was elastic/kibana#167505 which lead me to dig into the span parent IDs.
We have many other instrumented services, most not sending Azure ServiceBus messages which do not encounter this issue. The few services that do send to the ServiceBus, do have this UI error in Kibana.

To Reproduce

Steps to reproduce the behavior:

  1. Add a reference to the Azure.Messaging.ServiceBus Nuget package. We are using 7.17.2.
  2. Create a ServiceBusClient and use that to create a ServiceBusSender for a topic.
  3. Within a transaction, use the ServiceBusSender to send a ServiceBusMessage with SendMessageAsync().
  4. See recursion errors in Kibana APM transaction view when viewing the transaction.
    image
  5. See spans referencing themselves as the parent in Discover view.
    image

Expected behavior

To be able to see the transaction in Kibana without recursion errors.

Actual behavior

Recursion errors.

@sluebbert sluebbert added the bug Something isn't working label Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant