Requests from activity function are logged but not correlated with durable function telemetry #2729
Unanswered
ErdmanCT13
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to get distributed tracing set up on a project using durable functions.
In the process of setting up, I was able to get distributed tracing working with app insights, but the
operation_id
used by the DF telemetry isn't being passed along to downstream requests as I had hoped it would. We call activity functions from inside our orchestrator and then make requests from inside those activity functions which I've confirmed are logged to Application insights, but somehow not ending up correlated with the rest of the telemetry. At first glance this seems like a pretty basic use case so I'm hoping there's a solution.This is what our distributed traces look like in Application Insights. Take note of the fact that none of the automated telemetry produced from inside our activity functions appears.
my host.json file is set up in the following manner
After taking a look at the documentation and examples provided here https://github.com/Azure/azure-functions-durable-extension/tree/dev/samples/distributed-tracing/v2#:~:text=Async%20HTTP%20APIs%20(currently%20not%20shown%20in%20traces), it's not clear to me whether the request telemetry being omitted from DF distributed traces is intentional or if I'm perhaps doing something wrong.
Beta Was this translation helpful? Give feedback.
All reactions