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
The .NET SDK is still implementing User Feedback using a USER_REPORT_ENVELOPE which means feedback has to be associated with exception events (an eventid is required in the envelope).
Since then a new Feedback Events format has been introduced that allows User Feedback to be sent independently of exceptions. The .NET SDK. should also support Feedback Events.
This involved a new function: CaptureFeedback.
This function is the base functionality needed to allow capturing user feedback while including tags, replay_id, trace_id, etc.
It's part of the 'new user feedback' product (getsentry/sentry#64671) that was shipped for Web. That included a built-in widget, that allows screenshot attachment, and under the hood relies on this new function that deprecates the old CaptureUserFeedback which required an event_id. The new function optionally takes a related event_id and will contain relevant context stand alone.
This means a new envelope format for feedback was introduced.
The new Feedback product architecture has thoroughly documented by @aliu39 here:
Originally posted by @jamescrosswell in #3604
The .NET SDK is still implementing User Feedback using a
USER_REPORT_ENVELOPE
which means feedback has to be associated with exception events (an eventid is required in the envelope).Since then a new Feedback Events format has been introduced that allows User Feedback to be sent independently of exceptions. The .NET SDK. should also support Feedback Events.
This involved a new function:
CaptureFeedback
.This function is the base functionality needed to allow capturing user feedback while including tags,
replay_id
,trace_id
, etc.It's part of the 'new user feedback' product (getsentry/sentry#64671) that was shipped for Web. That included a built-in widget, that allows screenshot attachment, and under the hood relies on this new function that deprecates the old
CaptureUserFeedback
which required anevent_id
. The new function optionally takes a relatedevent_id
and will contain relevant context stand alone.This means a new envelope format for feedback was introduced.
The new Feedback product architecture has thoroughly documented by @aliu39 here:
This new function will allow outgoing feedbacks to be tied to Session Replay, which is currently Open Beta and we're working on GA:
The
develop
docs have not been added yet, but the ticket with details about it is here:Relates to:
captureFeedback
sentry-dart#2230SentryFeedbackWidget
sentry-dart#2369sendFeedback
tocaptureFeedback
& enhance it sentry-javascript#10953trace_id
allows the product to show all related telemetry collected during that traceThe text was updated successfully, but these errors were encountered: