-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Messages from User Feedback shouldn't be dropped by quotas and rate limits!! #71017
Comments
Assigning to @getsentry/support for routing ⏲️ |
Routing to @getsentry/product-owners-user-feedback for triage ⏲️ |
@ebelair Thanks for the feedback! It sounds like you're worried that a user might spend all this time to write a message, and you point out how it would be terrible if that message got dropped due to quota or something like that. Well good news... there's no quota for user submitted feedback! We do have The idea is that we don't need to put quota on this, and we're not charging for it. Here's some of the philosophy:
That doesn't mean that everything is without quota. Errors are Replays are submitted before the feedback, so quota will be used even before the user starts to type out their message. Also the screenshot feature is built on top of our attachments infrastructure which should have sufficient space on all plans for 100's or 1000's of images per month, depending on the screen size of users. |
If you've got more questions lmk, otherwise you will be able to see every feedback that hits our servers! |
@ryan953 Thanks for replying! Unfortunately, what you're saying does not seem to be the case. Our account was maxed out on errors and we were unable to see User Feedback come through... and as soon as we provisioned more errors, it started getting in again. I reached out to customer support and they thought this happened as intended – if you want to follow-up, our support case was no. 121621. Thanks so much! |
Problem Statement
Yes, quotas and rate limits are important to manage noisy projects, but...
With this User Feedback feature, we should make sure that those errors always go through. If a specific user has taken their time to write a note, and send it our way... It's kinda sad to see it capped out at the source...! 😞
Otherwise there would need to be a way to turn off feedback collection if we already know it's not likely to go through... Just to be respectful of our users' time, and not ask them for feedback if it's about to be trashed immediately anyway 🧠➡️🗑️
Solution Brainstorm
I think we should either:
Product Area
User Feedback
The text was updated successfully, but these errors were encountered: