Option to redact part of the URL within a Session Replay #8127
Assignees
Labels
Comments
|
Routing to @getsentry/product-owners-replays for triage, due by Tuesday, May 16th at 11:00 (yyz). ⏲️ |
billyvg
added a commit
that referenced
this issue
May 17, 2023
Allows you to modify/filter custom recording events for replays. Note this is only a recording event, not the replay event. Custom means that the events do not relate or affect the DOM recording, but rather they are additional events that the Replay integration adds for additional features.
This adds an option for the Replay integration `beforeAddRecordingEvent` to process a recording (rrweb) event before it is added to the event buffer. Example:
```javascript
new Sentry.Replay({
beforeAddRecordingEvent: (event) => {
// Filter out specific events
if (event.data.tag === 'foo') {
return null;
}
// Remember to return an event if you want to keep it!
return event;
}
});
```
Closes #8127
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement
Currently, it is possible to redact part of the URL for Errors and Transactions using
addGlobalEventProcessorto modifyevent.request.urlandevent.request.headers.For example, if the URL is
/Redactme-xyz, this can be changed to/[REDACTED]-xyz.However, this does not seem to work for Session Replays.
The requirement is for the addGlobalEventProcessor configuration to apply to Session Replays or to have a separate data scrubbing option in place to scrub/redact this data.
Solution Brainstorm
No response
Product Area
Replays
The text was updated successfully, but these errors were encountered: