Skip to content

Request cutoff browser side #2272

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

Closed
jawetzel opened this issue Oct 14, 2019 · 1 comment
Closed

Request cutoff browser side #2272

jawetzel opened this issue Oct 14, 2019 · 1 comment
Labels
Package: browser Issues related to the Sentry Browser SDK

Comments

@jawetzel
Copy link

jawetzel commented Oct 14, 2019

Package + Version

  • [+] @sentry/browser

Description

Loving the sentry product as a tool to debug.

It would help a ton if on the front end we could cut off a user after x number of requests by session.

On a regular basis we see a couple thousand errors(over a month), but every once in a while we see 10k events from 1 user (all the same event type in 1 day) and we would like to cut them off on multiple layers (including having sentry stop working on the front end).

I saw the thread discussing maxPerPage and maxPerSession, (#767) but it didn't seem to go anywhere. While I did see the rate limiting by sample .1 for 1/10th of the events getting through, and this may help cut down the volume some, it is still going to be thousands of events where I would like to cut them off at 50 in a session. (we do use breadcrumbs)

@smeubank
Copy link
Member

https://docs.sentry.io/product/accounts/quotas/manage-event-stream-guide/

Is this something which could be at least partially managed by spike protection?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Package: browser Issues related to the Sentry Browser SDK
Projects
None yet
Development

No branches or pull requests

3 participants