Closed jesanfafon closed 4 years ago
Hi @jesanfafon , thanks for reporting this. We've just released version 1.18.0 which should address this issue. Can you upgrade to this version and let us know if you're still seeing this issue?
Hi @zacharycmontoya 1.18.0 fixes the issue for us! Thank you very much!
Describe the bug We have an ASP.NET app with many legacy components. SQL queries made from the Microsoft.Practices.EnterpriseLibrary.Data library are not traced in 1.14.2 and later. I believe the reason for this is the same reasons discussed in #688 . However, adding the
DD_TRACE_DOMAIN_NEUTRAL_INSTRUMENTATION
environment variable didn't restore the spans in our traces, so I wonder if there's something else going on here.To Reproduce Steps to reproduce the behavior:
Expected behavior Queries going to sql server should be traced regardless of the library making the ADO.NET calls
Runtime environment (please complete the following information):
Additional context We're weighing the option of rewriting the code we have using the EPL to use plain ADO.NET instead, since the degree of change to do that is relatively minor. I wanted to file this bug, though, so that you guys know about it 😄