-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Filtering IP address in Settings - Which option covers what? #5916
Comments
Routing to @getsentry/ingest for triage. ⏲️ |
Hi @larsqa, basically if you use But there is also possibility to turn the data scrubbing of the IPs off, as you can see. And you can then, by yourself, add an advance data scrubbing rule, to scrub the IPs only in some specific places. And leave out the rest no scrubbed. Does this answer your question? |
Is this both for exception and transaction payloads?
Basically, the |
@olksdr I have just been in touch with @rhcarvalho via a support ticket. Here is stated:
The description under the toggle states:
Which one is it now? Does
|
The one in Advanced Data Scrubbing is more general, scrubbing by regex. |
@jjbayer - the link you provided is from the relay repo. My app doesn't use relay. Does this still apply? |
Alright - good to know this! Wouldn't it make sense to update the text below the setting in the dashboard? It may confuse users to fully trust that setting to filter out from the full payload. |
Will check with the team if we actually want to expand the behavior of |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Core or SDK?
Core Sentry product
Which part? Which one?
Core Sentry
Description
In Sentry, you have several options to remove IP addresses from being stored.
Suggested Solution
The documentation fails to highlight the difference between the two. Which cases do they cover?
The text was updated successfully, but these errors were encountered: