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.

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

Feature Request: BlueScreen Data Anonymization #328

Closed
JanTvrdik opened this issue Oct 29, 2018 · 3 comments
Closed

Feature Request: BlueScreen Data Anonymization #328

JanTvrdik opened this issue Oct 29, 2018 · 3 comments

Comments

@JanTvrdik
Copy link
Contributor

@JanTvrdik JanTvrdik commented Oct 29, 2018

For both GDPR compliance & security reasons, it would be really helpful if Tracy supported some form of data anonymization.

@dg

This comment has been minimized.

Copy link
Member

@dg dg commented Oct 29, 2018

Can you prepare PR?

@JanTvrdik

This comment has been minimized.

Copy link
Contributor Author

@JanTvrdik JanTvrdik commented Oct 29, 2018

No in the near-term, and unlikely in the long-term.

@dg dg closed this in 144cb73 Oct 30, 2018
dg added a commit that referenced this issue Oct 30, 2018
Revert "Debug: removed $keysToHide, sensitive keys filtering"

This reverts commit 0b9e92b.
dg added a commit that referenced this issue Oct 30, 2018
Revert "Debug: removed $keysToHide, sensitive keys filtering"

This reverts commit 0b9e92b.
dg added a commit that referenced this issue Oct 30, 2018
Revert "Debug: removed $keysToHide, sensitive keys filtering"

This reverts commit 0b9e92b.
dg added a commit that referenced this issue Oct 30, 2018
Revert "Debug: removed $keysToHide, sensitive keys filtering"

This reverts commit 0b9e92b.
@JanTvrdik

This comment has been minimized.

Copy link
Contributor Author

@JanTvrdik JanTvrdik commented Oct 31, 2018

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.