-
Notifications
You must be signed in to change notification settings - Fork 11
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
Background periodic publisher doesn't recover from a network exception #8
Comments
Agreed - the current behavior is not great. The background thread should fail the whole process on error (relevant read) or continue publishing. In the meantime here are a couple suggestions to work around this:
|
Right, the only viable option in case of backend daemons is to carry on with (or without) delayed retrying to send the same payload again, as failing the entire process is hardly desirable. How about performing another |
If a trace collector is temporarily down, a background thread that tries to reach it is expected to survive
flushSpans
throwingConnectionFailure
:The text was updated successfully, but these errors were encountered: