-
Notifications
You must be signed in to change notification settings - Fork 445
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
Azure Functions does not support DiagnosticListener callbacks when using System.Diagnostics.DiagnosticSource (> 4.7.0) #7135
Comments
We need to track the unification change in 4.0. Tagging @brettsam for validation in v4 |
Haven't seen any PR tagged for this issue. Is it working now? |
Hi @ThomsonTan did this not work for you in V4? |
It should work in V4 and Otel 1.3.*. |
Should it work with non-isolated workers? What I see is that msbuild when building a function deletes the "System.Diagnostics.DiagnoticSource.dll" file (presumably by a
OpenTelemetry.Api/1.4.0 depends on that particular version of System.Diagnostics.DiagnosticSource. Setting |
@agr 7.0.0 dependencies will not work in Azure Functions 4.0 (in-proc) with the unification rules it has. If you need to use 7.0.0, the recommendation is to use the Isolated (out-of-proc) model. |
Closing this as resolved |
DiagnosticListener callbacks are not called in Function apps when using System.Diagnostics.DiagnoticSource (> 4.7.0)
Investigative information
Tried this locally
Repro steps
Expected behavior
Response should be:
This is a list of events that are logged by HttpClient when making an outbound Http request
Actual behavior
Response is empty
Known workarounds
Revert the System.Diagnostics.DiagnosticSource package version to 4.7.0
Related information
The text was updated successfully, but these errors were encountered: