Open williazz opened 3 months ago
One immediate issue is that RUM disables itself when the number of retries has been exhausted due to network failure. Disabling makes sense when there is a client misconfiguration, such as invalid credentials (403) because retries will never succeed. But this poor practice when it's due to network condition because that might recover, in which case RUM is needlessly disabled.
Please help to prioritize the fix where RUM disables itself when the number of retries has been exhausted due to network failure or other error codes like 401, 307 etc. RUM should not disable in such scenario and should continue to emit metrics.
We do not want to remove this feature entirely because RUM should disable when we know that retries will never succeed, such as when credentials are invalid.
To solve the immediate problem, we can add configuration such as disableOnFailure: boolean
. And we'd want to make sure that this config is extensible for when provide full offline support.
sure as an immediate solution the above config will work. Thanks, Also Could you please provide an ETA.
I've merged in the feature to keep RUM alive when dispatch fails. To close out on this issue, we need to figure out an offline strategy that users can opt into.
Open question:
When network connection is offline, RUM should cache events and dispatch them to the collector when the connection recovers.