Azure function queue trigger distributed tracing

Question

I have a .NET isolated function with a queue trigger.

When triggering that queue from the storage explorer or from another function using a QueueServiceClient, a new operationId is made up. Thus I cannot correlate it, it seems.

Is it possible to do distributed tracing using W3C standard for Azure Function Queue trigger? I can not find any source on this.

If so, how?

can you provide some more information so that community will help to solve your query. — Delliganesh Sevanesan
– Delliganesh Sevanesan, Commented Oct 17, 2022 at 10:10
@DelliganeshSevanesan I will find some time to create a minimal example. But the gist of the question is how to enable e2e tracing following W3C Trace Context specification on Queue Triggered Functions. I will provide an example soon. — XWIKO
– XWIKO, Commented Oct 18, 2022 at 7:52

XWIKO · Accepted Answer · 2022-10-20 10:11:26Z

0

Currently not supported. Azure Functions team will evaluate this scenario (at some unmentioned point in time) whether or not it can be/will be supported. This has to do with their dependency on the team creating the Azure.Storage.Queues SDK.

https://github.com/Azure/azure-functions-dotnet-worker/issues/1126

edited Oct 20, 2022 at 10:11

answered Oct 20, 2022 at 9:57

XWIKO

3435 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Wojciech Rak Over a year ago

Any update on that? @XWIKO

XWIKO Over a year ago

Hi @WojciechRak They mentioned 3 weeks ago that it is not possible still. Also does not look like they are going to be working on that. github.com/Azure/azure-functions-dotnet-worker/issues/…

Collectives™ on Stack Overflow

Azure function queue trigger distributed tracing

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related