-
Notifications
You must be signed in to change notification settings - Fork 14
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
Telemetry sporadic crash due to HTTP timeout #478
Comments
Hi @charettes Can you share the version of the SDK, any logs that you have regarding the crash, and your SDK config parameters? Likewise, are you able to reproduce this issue? Regards, |
We are using
|
Hi @charettes The telemetry config call happens only when the SDK is initializing, not ongoing. Regards |
@hbqdev there is an unhandled exception in the thread that crashes it but does crash the thread itself. Since it's a benign error we'd like a way to silence it entirely either by disabling telemetry entirely or by having the error redirected to a logger than we can silence. The error happens in |
Hi @charettes Regards |
Hi @charettes Regards |
Thank you @hbqdev I'll update to 9.6.0 and report if it addresses the issue. |
Thank you @charettes |
We're experiencing sporadic crashes of the thread in charge of sending telemetry to split.io and it's polluting our logs with unnecessary noise.
Is it possible for
TelemetryAPI
not to crash withAPIError
when it encounters errors duringrecord_*
method and simply direct them to a logger that can be silenced?Alternatively is it possible to disable Telemetry entirely as it's not a feature we're interested in?
The text was updated successfully, but these errors were encountered: