Description
This is a proposal to enable disk-buffering out of the box for the agent initialization. The agent initialization is supposed to contain all of our "opinions" on what parts of core/RUM should be enabled and how they should be configured so that the agent behaves well for most of the end-user use cases without having to write much code.
Storing signals on disk is crucial to avoid data loss, especially in mobile environments, so it makes sense to me that this feature should be enabled by default as part of the agent initialization. There might be reasons why disk buffering should be disabled in some cases, although my understanding is that those would be exceptional ones. Therefore, should we decide to enable it by default in the agent, we should include a config option to optionally disable it.
I'm looking forward to any opinions on this proposal before creating a PR to apply the changes to enable it by default, in case I missed something important that requires it to be kept disabled by default.