We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
long scopeID = SqlClientEventSource.Log.TrySNIScopeEnterEvent("<sc.SNI.SNIMarsHandle.SendAsync |SNI|INFO|SCOPE>");
is logged in the following methods:
SNIMarsHandle.SendAsync
SNIMarsHandle.ReceiveAsync
SNITcpHandle.SendAsync
Each method should have a distinct message corresponding to the method name in which it is logged
Microsoft.Data.SqlClient version: 2.1.2
The text was updated successfully, but these errors were encountered:
Hi @nickljones
We're improving this design in future versions. It's a huge effort so it's being done in parts. (ref: PR #897)
Sorry, something went wrong.
Closing this as PR #897 was merged. Feel free to open a new issue if the concern is not addressed yet.
No branches or pull requests
Describe the bug
long scopeID = SqlClientEventSource.Log.TrySNIScopeEnterEvent("<sc.SNI.SNIMarsHandle.SendAsync |SNI|INFO|SCOPE>");
is logged in the following methods:
SNIMarsHandle.SendAsync
SNIMarsHandle.ReceiveAsync
SNITcpHandle.SendAsync
Expected behavior
Each method should have a distinct message corresponding to the method name in which it is logged
Further technical details
Microsoft.Data.SqlClient version: 2.1.2
The text was updated successfully, but these errors were encountered: