A duplicate diagnostic entry was renamed from Azure Service Bus transport to Azure Service Bus transport-X

I’m getting a lot of tracing messages, but I don’t know why.

The message is below and it sometimes it goes all the way up to above 100:
A duplicate diagnostic entry was renamed from Azure Service Bus transport to Azure Service Bus transport-2

This is in an Azure function v4 (.NET6 ISolated) with Azure Service Bus. I don’t see any other logging connected to this operation in Application Insights.

This function is scheduled every

Seems to be related to Write the diagnostic file when duplicate entries exist by HEskandari · Pull Request #5688 · Particular/NServiceBus (github.com).

NServiceBus/HostStartupDiagnosticsWriter.cs at d00253f600d5317a97c05aca36a9d6ffed53b16d · Particular/NServiceBus (github.com)

fixed by answer in With NSB 8 I'm getting ServiceBusException: Cannot allocate more handles. The maximum number of handles is 255 - #4 by danielmarbach