aliu39
commented
1 month ago The linked PR truncates messages to 4096 characters on Sentry backend, and doesn't error. It is not aware of bytes/encodings, since this is way after envelope processing. This is meant as a temporary measure before we add limits in the envelope schema, and dropped outcomes in Relay.
Until we have updates on the schema, I'd recommend documenting "4096 characters max per message".
getsantry[bot]
Which section?
SDK -> Expected Feature -> User Feedback
Page URL
https://develop.sentry.dev/sdk/expected-features/#user-feedback
Description
Copying from the old repo, which got archived:
The current User Feedback SDK is documented here: https://develop.sentry.dev/sdk/features/#user-feedback
With the new feedback product allowing for capture of feedback outside errors. With the ability to include attachments (e.g: screenshots), tags, and other user context. The protocol has been expanded.
A new API is also being done on JS. Aligning on a new function captureFeedback. The previous captureUserFeedback can be deprecated in favor of the new.
The eventId that we took before is now optional. And the plan is to rename it to something else since the feedback itself will have an id, and eventId is ambiguous.
Document the new envelope format too. Mark the old one as deprecated.
This will unblock in particular the Mobile SDKs
Relates to:
https://github.com/getsentry/sentry-javascript/issues/10953
https://github.com/getsentry/develop/issues/1208 Worth linking/connecting the two docs ^
[ ] Document max length based on @aliu39 's change (specifcy units, like bytes, not characters) (https://github.com/getsentry/sentry/pull/79326)
Suggested Solution
Clarify the new API and guidelines