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
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)
The text was updated successfully, but these errors were encountered:
[+] Review the documentation: https://docs.sentry.io/
[+] Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
[+] Use the latest release: https://github.com/getsentry/sentry-javascript/releases
[+] Provide a link to the affected event from your Sentry account
https://sentry.io/organizations/lipseys/issues/1270339762/?project=180610&query=is%3Aunresolved
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)
The text was updated successfully, but these errors were encountered: