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

Investigate SDK back pressure issues #2360

Open
denrase opened this issue Oct 15, 2024 · 1 comment
Open

Investigate SDK back pressure issues #2360

denrase opened this issue Oct 15, 2024 · 1 comment
Assignees

Comments

@denrase
Copy link
Collaborator

denrase commented Oct 15, 2024

Description

A user reported that calling sentry capture methods in fast succession is leading to issues, especially with screenshot integration.

Investigate if calling the SDK mehods in tight loops can be improved. One idea was to introduce a debounce for screenshots.

The minimal repro steps I got are attached, but this is a heavily contrived example aimed at easily reproducing the issue. In practice this would look like 30 API requests in short succession that all fail due to no internet connectivity or where all endpoints return an error code, where Sentry then creates exceptions in short succession.

Image

@denrase denrase self-assigned this Oct 15, 2024
@buenaflor
Copy link
Contributor

fyi, the real example could lead up to 75 api calls due to heavy retries (for example with bad internet connection)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Needs Discussion
Development

No branches or pull requests

2 participants