Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create RFC on how to improve control over handling of sensitive data #8

Closed
antonpirker opened this issue Jan 12, 2023 · 0 comments · Fixed by getsentry/rfcs#62
Closed

Create RFC on how to improve control over handling of sensitive data #8

antonpirker opened this issue Jan 12, 2023 · 0 comments · Fixed by getsentry/rfcs#62
Assignees
@sl0thentr0py
Labels
RFC RFCs related work

Comments

@antonpirker
Copy link
Member

Right now one can control what sensitive data is collected with:

  • the sendDefaultPII option
  • beforeSend hook
  • beforeSendTransaction hook
  • event processors (but only for internal use)

We need to improve this to give the users an easy and concise way to customize how their sensitive data is and what data is collected.

Lets create an RFC to specify how we want to control sensitive data.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sl0thentr0py sl0thentr0py

Labels
RFC RFCs related work
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

rfc(feature): Controlling PII and Credentials in SDKs getsentry/rfcs
2 participants
@antonpirker @sl0thentr0py