[Event Hubs] Tracing: Periodic calls to getEventHubProperties reported on unrelated operation

[yoshigev]

• Package Name: @azure/event-hubs
• Package Version: 5.12.2
• Operating system: Linux
• nodejs
  • version: 22.10.1
• browser
  • name/version: N/A
• typescript
  • version: 5.7.2
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://learn.microsoft.com

Describe the bug
We have a NodeJS service that sends events to an event hub as part of handling an incoming HTTP request.

We use Application Insights, and when looking at transaction of the first HTTP request that the service has handled, we see that there are many unrelated logs that are reported on this HTTP request.

The logs are of a periodic tasks that starts with "EnvironmentCredential.getToken" and ends with "ManagementClient.getEventHubProperties", as seen in the screenshot below.

To Reproduce
Send events as part of an HTTP transaction.

Expected behavior
I expect that those periodic tasks will use their own operation without a parent.

Screenshots

Additional context
I have several questions regarding this behavior:

1. Is the periodic task really needed if we're just the producer and not the consumer?
2. Just came to my mind that we are actively calling the method client.getPartitionIds() as an health check. Can it be the trigger to my problem?
3. Looking for a workaround - Is there anything besides sending an actual event that can trigger the periodic job, so I could start it outside any context?

Thanks,

Yehoshua

[deyaaeldeen]

Hi @yoshigev, thank you for opening this report.

Is the periodic task really needed if we're just the producer and not the consumer?

The client is built on the AMQP protocol, where the connection is established once and persists. To ensure proper client authentication and authorization, the periodic task is essential.

Just came to my mind that we are actively calling the method client.getPartitionIds() as a health check. Can it be the trigger to my problem?

The getPartitionIds method internally invokes getEventHubProperties, so it’s expected to see traces of the latter in your insights.

Looking for a workaround - Is there anything besides sending an actual event that can trigger the periodic job, so I could start it outside any context?

The getPartitionIds method accepts a tracingOptions option, which might provide a way to adjust the tracing behavior. @mpodwysocki, do you have any suggestions on how we might assign the getPartitionIds trace to a distinct parent?