-
Notifications
You must be signed in to change notification settings - Fork 91
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
ASP.NET intrumentation failed on .NET framework #2833
Comments
web.configs.zip |
Some suspicions, but, not clear to me yet exactly what is the problem. The current top hypothesis is that the binding redirect for @muhaook could add/update the package reference to https://www.nuget.org/packages/System.Diagnostics.DiagnosticSource/7.0.2 and give it another try? Please, share the resulting web.config files and traces. Thanks! |
Thanks @pjanotti for taking care of this issue I am not sure if I added the suggested package reference to project Attached please find logs and web.config files: That said, if customer hit similar issue, we can suggest them to add the suggested package reference, but they may have concern to add a package reference that they did not have to reference to explicitly. |
Thanks @muhaook - I'm going to keep the issue open until I have a chance to look at the newer logs. Likely we need to at least to add something to troubleshooting. |
SIG: troubleshoot note for GA. |
Describe the bug
ASP.NET intrumentation failed sometimes on .NET framework.
I have 2 webapi ASP.NET applications. One is
WebApiMySql80Netfx462
; the other isWebApiMySql81Netfx462
. I accessed the first application and saw the ASP.NET instrumentation succeeded. after that, when I tried to access the second application, I did not see any ASP.NET trace/span got collected. Looks like the second ASP.NET instrumentation failed. If I access the second web app in the first place, its traces/spans can be collected.Attached please find logs:
logs_aspnet_instrumentation_failure.zip
Runtime environment (please complete the following information):
The text was updated successfully, but these errors were encountered: