-
Notifications
You must be signed in to change notification settings - Fork 759
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
Named tracers with DiagnosticSources #251
Comments
The approach I've been thinking about it:
Stay tuned for the PRs |
* Update CHANGELOG for Quartz Instrumentation
Named tracers being introduces in #239 is intended to provide different behavior for different instrumentations (sampling, filtering, etc)
.NET/Microsoft provided libraries are typically instrumented with DiagnosticSource + Activity. DiagnosticSource already has filtering mechanisms that prevent any instrumentation from happening and performance-wise are better than named tracers.
We should define and implement how they would work together while keeping best performance we could get.
The text was updated successfully, but these errors were encountered: