-
Notifications
You must be signed in to change notification settings - Fork 341
Instrument with DiagnosticSource #471
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
Comments
Do you know if there's a "standard" or documentation for typical ADO.NET diagnostic events? Or is each provider supposed to implement it in an idiosyncratic way? I found this example for SqlClient; didn't find any usage within Npgsql or Microsoft.Data.Sqlite. |
@bgrainger |
There is not such a diagnostic "standard", you just need to name your diagnostic source and event following your naming convention, and specify the event specific payload. In general, you can provide the following instrumentation activities:
For each instrumentation activity, it's better define the following events:
The following is a demo:
You can also provide more antagonistic payload like System.Data.SqlClient. |
Hello folks. We really need this functionality. We need it for integration with OpenTracing. May be is there any way we can help you do this? |
I haven't looked into OpenTracing much yet. Would it be possible to integrate with OpenTracing by writing a wrapper |
Is/has anyone picking/picked this up? |
Just answered here: #493 (comment) |
Superseded by #1036. |
Available in 2.0.0-beta.5. |
Hello , Thanks for the great work.
I'm working on APM-related work. Using diagnostics allows users to get more runtime event data, which is helpful for distributed tracking systems.
EntityFramewokCore has provided support for diagnostics, but if users do not use EF, it is difficult for them to obtain these event data, so is there any plan to provide some diagnostic event data at the driver level?
Diagnositics doc :
https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.DiagnosticSource/src/DiagnosticSourceUsersGuide.md
The text was updated successfully, but these errors were encountered: