-
Notifications
You must be signed in to change notification settings - Fork 765
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
Catch exceptions in flush timer and write to EventSource #696
Catch exceptions in flush timer and write to EventSource #696
Conversation
@Illia-M You'll need to sign the CLA as this is your first time! |
In progress, but it can take a while... |
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Illia-M. Looks good, just one suggestion to move the try/catch inside FlushAsyncInternal.
Thanks @Illia-M - LGTM. |
Looks like you'll need to update your PR with recent master branch changes before we can merge. |
Updated |
…ry/opentelemetry-dotnet into batching-activity-processor * 'batching-activity-processor' of github.com:open-telemetry/opentelemetry-dotnet: Catch exceptions in flush timer and write to EventSource (#696)
Fixes #695 .
Changes
In JaegerUdpBatcher on flush timer tick exceptions in async void method cause application crash due to unhandled exception.
Add JaegerExporterEventSource and log handled exceptions on flush try from timer tick.
Checklist
For significant contributions please make sure you have completed the following items:
The PR will automatically request reviews from code owners and trigger CI build and tests.