-
Notifications
You must be signed in to change notification settings - Fork 248
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
Handle exceptions from Exporters #270
Comments
+1 to this. Sometimes the Stackdriver Exporter can't contact the Stackdriver APIs temporarily and makes the whole background thread crash. |
Frequently getting the following exception with the StackdriverExporter, which seems caused by transient unavailability in the metadata service, and crashes the
We should add retry logic to the
Should we do this to all the exporters contacting remote APIs to make sure we're not crashing the collection thread ? |
Actually I think we should just make sure the |
This is linked to googleapis/google-auth-library-python#211 |
Is the client's default here actually retrying? I'm seeing instances of singular 503's without retries. Thanks to #297 it doesn't crash anything, but 1) I do get an error in reporting and 2) the items get dropped from the queue. |
Currently if there's an exception while emitting spans,
BackgroundThreadTransport
will stop working.Should it be up to the exporters themselves to handle exceptions? There could be some weird interactions in that case, for example, if the exporter sleeps to retry when using
SyncTransport
.The text was updated successfully, but these errors were encountered: