Dependency Tracking for Always Encrypted Connection in ASP.NET Core 2.2

[lsuarez5280]

Hello. I wish I had more specifics around the limitations here, but I've had to transition to the Microsoft.Data.SqlClient package in order to support Always Encrypted with my ASP.NET Core 2.2 application. This has the unfortunate effect of eliminating automatic wireup of SQL dependency tracking. I admit I don't fully know what events Application Insights hooks in order to facilitate SQL dependency tracking in Core, so I'm at a loss as to how to restore this to my impacted applications that have had to replace their SqlConnection factory and ISqlConnection implementation for Entity Framework Core 2. Could someone potentially point me to any place they might know of that I can reattach dependency tracking to this SqlClient, or at least how this is done in the current codebase so I can try to replicate functionality?

Currently using the Microsoft.ApplicationInsights.AspNetCore 2.8.2 package.

[lmolkova]

Please start with https://github.com/dotnet/SqlClient. They should be able to share any behavior in DiagnosticSource hooks that is affected by Always Encrypted mode.

This is the code AppInsights is hooked to: https://github.com/dotnet/SqlClient/blob/654933a0811ab30b843a20aff051b8d585238505/src/Microsoft.Data.SqlClient/netcore/src/Microsoft/Data/SqlClient/SqlClientDiagnosticListenerExtensions.cs

[lsuarez5280]

Thanks @lmolkova. I appreciate the pointers and will post back if I have further inquiries, along with a solution if I have one.

[lsuarez5280]

Leaving a trackback to dotnet/SqlClient#93 since it's related to this question.

[lsuarez5280]

@lmolkova Actually after reviewing SqlClientDiagnosticSourceListener.cs on the latest beta release, this library appears to be supported, so please disregard this issue. I'll close for now and reopen if it's not what I anticipated.