Skip to content
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

Report key events to dotnet diagnostics infrastructure. #9

Open
sanych-sun opened this issue Feb 9, 2023 · 0 comments
Open

Report key events to dotnet diagnostics infrastructure. #9

sanych-sun opened this issue Feb 9, 2023 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@sanych-sun
Copy link
Owner

sanych-sun commented Feb 9, 2023

Consider raising events into dotnet diagnostics infrastructure to cover key points in the library life-cycle. Have to investigate and implement counters (for number of delivered or published messages for example), report key events (for example, connection open, connection broken, etc) as well as some way to report a time spend by different components of the library (for example, time of serialization).

Use full links:
https://learn.microsoft.com/en-us/dotnet/core/diagnostics/distributed-tracing
https://learn.microsoft.com/en-us/dotnet/core/diagnostics/diagnosticsource-diagnosticlistener

@sanych-sun sanych-sun added the help wanted Extra attention is needed label Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant