-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
User Feedback Feature Request: Custom context #10916
Comments
Assigning to @getsentry/support for routing ⏲️ |
Routing to @getsentry/product-owners-user-feedback for triage ⏲️ |
Thanks for raising. This makes sense and on v8 of the JS SDK we plan to align the |
in v8, you can add any data via the scope, which will be picked up by the feedback event like any other event. You can do either this: Sentry.captureFeedback(
{ message: "I really like your App, thanks!" },
{
captureContext: {
tags: { key: "value" },
extra: { key: "value" },
},
}
); Or you can put data on the scope, which will be automatically picked up as well: Sentry.withScope(scope => {
scope.setTag('my-tag', 'value');
Sentry.captureFeedback({ message: 'My feedback goes here!' });
}); |
Problem Statement
Use case: When an error occurs, we prompt the user for feedback and also for consent to upload diagnostic info. Diagnostic info is uploaded to cloud storage, and I'd like to associate the cloud storage URI with the event created in Sentry. This URI is only generated after the user consents to uploading diagnostics, so it's not available at the time of the crash. This is very similar to https://forum.sentry.io/t/updating-event-after-initial-upload/15057 but I didn't see a solution for that issue.
For user feedback that isn't related to a crash, we can do:
However, for user feedback for a crash report, I don't see a way of attaching this context to the original event.
Workarounds:
I'd rather not do either of these options but I suppose they could work:
Let me know if there are other options I should consider.
Alternatives:
Solution Brainstorm
No response
Product Area
User Feedback
The text was updated successfully, but these errors were encountered: