-
Notifications
You must be signed in to change notification settings - Fork 123
SQL Dependency has wrong parrentId #778
Comments
thanks for reporting this.
You've upgraded the SDK to 2.5.1?
|
|
They are random and do not have any personal or sensitive information. If your policies do not allow to share them publically, could you consider sending them over email to me? (my email is in the profile). you may run query that returns only Ids and won't reveal any information to me
Another option could be a small repro app. Also, where do you make db call? Is it during message processing within a processing handler? |
I think I have the same issue, see my stackoverflow question: https://stackoverflow.com/questions/53322973/disable-ef-core-migration-verification-query |
Closing as this is fixed in linked PR |
Repro Steps
Actual Behavior
Requests logged correctly, API call is child,
SQL Server call is NOT a child of root request. It is on the same level with request
Expected Behavior
SQL Server dependency should have request as parrent
NOTE: workaround is to store RequestId in Activity when request starts, and set parrentId in sql dependency in custom telemetryProccessor
Version Info
SDK Version : Microsoft.ApplicationInsights.AspNetCore Version=2.3.0 - 2.5.1
.NET Version : netcoreapp2.1
The text was updated successfully, but these errors were encountered: