Skip to content
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

Add a debouncer #22

Open
bitsandfoxes opened this issue Nov 21, 2024 · 1 comment
Open

Add a debouncer #22

bitsandfoxes opened this issue Nov 21, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@bitsandfoxes
Copy link

It’s easy for the SDK to end up capturing a ton of errors in a short amount of time. For example, if there's a script error in _process, the SDK can capture every single one. This could quickly burn through a user’s quota without providing much helpful info.

Why this is a problem

  • You can blow through your quota super fast i.e. with errors in _process or _physics_process
  • Sending a bunch of errors in one go could impact performance, especially during gameplay.
  • A bunch of duplicate errors are not going to be terribly useful anyway

How this could help

Adding a debounce feature would make error reporting smarter by:

  • Limiting frequency: Only capturing one error every X seconds, for example. We have a very naive implementation like this in the Unity SDK
  • Skipping duplicates: If the same error happens repeatedly (like in a loop), don’t capture it every time. But how would we detect duplicates?
@limbonaut
Copy link
Collaborator

limbonaut commented Nov 21, 2024

how would we detect duplicates?

Maybe keeping a count keyed by (file, lineno)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

2 participants