-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TraceContext: TraceParent and TraceState properties are always empty. #410
Comments
This is currently a gap that @brettsam has been tracking. We'll continue to use this issue to track the work. Thank you! |
I am waiting for the same, when will going to be supported? |
Today you need to have Application Insights enabled for this to work. The host will eventually move to using the newer OpenTelemetry instrumentation so these traces flow without App Insights, but for now, App Insights is required. |
If you're trying to get this working with Application Insights, try the new preview packages: #944 (comment) |
I've filed Azure/azure-functions-host#8846 to track removing the Application Insights requirement. |
I'm trying to setup distributed tracing in .NET 5 and as a minimum I would like to see the dependency calls of a .NET 5 worker function call in Application Insights.
I expected the worker to set
System.Diagnostics.Activity.Current
when processing a function invocation, but that is not the case.So I wrote a middleware which extracts the
TraceParent
andTraceState
properties into anActivitySource
:but the
TraceContext
properties are always empty. I don't know if this is an issue in de worker code, or an issue in the functions host.The text was updated successfully, but these errors were encountered: