Getting too much undiagnosable errors in Sentry for Flutter web

[NicolasDionB]

Problem Statement

Created in part from discussion #1718
We recently set-up Sentry in our project and now that it's in production and used by thousands of people we get a lot of errors and some are not quite useful. By that I mean that we get errors coming from the Flutter SDK or some obscure package. It would be useful if I could disable capturing such errors as I don't have a way to diagnose/fix them. Such an example is:

We use an Azure DevOps git repo. We upload the sources using sentry_dart_plugin, with the following config:

sentry:
  upload_debug_symbols: true
  upload_source_maps: true
  upload_sources: false
  project: live_app
  org: svi-esolutions
  wait_for_processing: false
  log_level: error
  commits: auto
  ignore_missing: true

Finally in my SentryFlutter init, I put the following options:

options.captureFailedRequests = false;
options.enableNativeCrashHandling = false;
options.enableTracing = false;

Solution Brainstorm

Maybe adding an option for this would be great, for instance options.enableSdkErrorCapture which could be disabled by default in my opinion.

Following the same idea, if it is possible, maybe we could have a distinct flag to capture errors coming from dependencies, something like options.enableDependenciesErrorCapture.

Are you willing to submit a PR?

None

[buenaflor]

After taking a look at it, the option inAppExcludes might fit your use case: see here

example : ['sentry'] will exclude exception from package:sentry/sentry.dart

[buenaflor]

Additionally for another alternative you can add stacktrace rules to your sentry project: https://docs.sentry.io/product/data-management-settings/event-grouping/stack-trace-rules/#mark-in-app-frames

so this will also apply to existing events and is not dependent on your SDK options.

[NicolasDionB]

After taking a look at it, the option inAppExcludes might fit your use case: see here

example : ['sentry'] will exclude exception from package:sentry/sentry.dart

Thanks for your ideas! I will have a try but looking at the documentation, for inAppExcludes, wouldn't that only exclude the packages or sdk from the stacktraces and still capture the errors originating from them? If an error occurs in my code and some package has something to do with it, I want to see their code also in my stacktrace. I just don't want exception that are thrown from their code to be captured by Sentry.

For your second comment, I'm not sure how to use that in my case but I will take more time to better understand the approach. But then again, the best solution would be to not capture at all these exceptions in the app, saving a lot of useless process sending them from the clients to Sentry everytime a render error occurs in the Flutter SDK...