search

Azure / azure-functions-servicebus-extension

Service Bus extension for Azure Functions
MIT License
65 stars 35 forks source link

Operation Id is lost from message producer to message consumer #129

Closed Anthony-Breneliere closed 2 years ago

Anthony-Breneliere commented 3 years ago

I have two function apps: receiver that send messages in a topic, and processor that receive messages from a subscription from that topic.

Before migrating processor to Azure Function V3, in application Insight, traces from receiver and processor have the same operation Id.

After migrating processor to Azure Function V3, a new operation Id is created for each message received by the processor function app.

That is an issue because application insight cannot make the link between the message received in the receiver and the message processed in the processor. Requests sent to application insight by the processor have a wrong operation Id.

To migrate processor to Azure Function V3, I had to add the following dependency in the .csproj in order to use ServiceBusTrigger:

<PackageReference Include="Microsoft.Azure.WebJobs.Extensions.ServiceBus" Version="4.1.0" />
alrod commented 2 years ago

operation-id correlation should work Microsoft.Azure.WebJobs.Extensions.ServiceBus 5.x. @Anthony-Breneliere, have you checked it?

ghost commented 2 years ago

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.