You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
General .NET implementations of Sentry support a CacheDirectoryPath option for enabling caching of events, should there be an interruption in Internet connectivity. A Blazor WebAssembly application can successfully run during an Internet outage. The existing option doesn't and can't work, since WebAssembly applications have limited access to the local file system. But, there are other options for caching events locally that Sentry could be taking advantage of.
Solution Brainstorm
Abstract the underlying storage mechanism used for caching and provide a mechanism for integrators to be able to define their own implementation. This actually solves this and other needs, as it would allow integrators to override the basic implementation, to target a database, for instance.
Provide an implementation behind an option that utilizes local storage for persisting events that need to be submitted to the server.
The text was updated successfully, but these errors were encountered:
@mdemler - Thanks for the feature request. I transferred this from the main Sentry repo, as it is specific to the .NET SDK. Please log .NET SDK issues to this repo (sentry-dotnet) going forward.
The abstraction is a good suggestion. We do actually have some abstraction already around our file system internals, but they are mostly designed for testing purposes at the moment. We can consider a future enhancement to expose an API for this, or perhaps to provide this automatically as a Blazor-specific Sentry package.
Neither are on the immediate plan, but we can keep this issue here to reference in the future.
Problem Statement
General .NET implementations of Sentry support a CacheDirectoryPath option for enabling caching of events, should there be an interruption in Internet connectivity. A Blazor WebAssembly application can successfully run during an Internet outage. The existing option doesn't and can't work, since WebAssembly applications have limited access to the local file system. But, there are other options for caching events locally that Sentry could be taking advantage of.
Solution Brainstorm
The text was updated successfully, but these errors were encountered: