Replies: 1 comment 1 reply
-
There's no such template. I believe this is unresolved but documented on the functions side. Agreed that something should be able to handle this, but there's no tooling detection on either side that understands a functions app is running. I think we'd need to work with the functions team to activate something in the core functions runtime if some configuraton were set from the apphost. cc @fabiocav |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using
AddAzureFunctionsProjectwith Aspire and the standard service defaults (AddServiceDefaults()). I wasn't seeing telemetry correlation between the Functions host process and the worker process in Application Insights -- traces appeared as separate, disconnected operations with no end-to-end distributed trace linking the host invocation to my function code.After some digging, I found that adding
UseFunctionsWorkerDefaults()from theMicrosoft.Azure.Functions.Worker.OpenTelemetrypackage resolved this:The Azure Functions OpenTelemetry documentation shows this call as required for .NET isolated worker apps. It:
Questions
AddServiceDefaults()intentionally not cover this, or is it an oversight that the Azure Functions template doesn't include it?Program.cs? It seems like anyone usingAddAzureFunctionsProjectwith Application Insights would hit this.AddServiceDefaults()handle this automatically when it detects it's running in an Azure Functions worker? Or would that conflict with the host-level OpenTelemetry configuration?What I observed without
UseFunctionsWorkerDefaults()Beta Was this translation helpful? Give feedback.
All reactions