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

log: instrument telemetry when PII redaction is enabled #51834

Closed
thtruo opened this issue Jul 23, 2020 · 1 comment · Fixed by #53263
Closed

log: instrument telemetry when PII redaction is enabled #51834

thtruo opened this issue Jul 23, 2020 · 1 comment · Fixed by #53263
Assignees
Labels
A-security A-telemetry C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Comments

@thtruo
Copy link
Contributor

thtruo commented Jul 23, 2020

We currently have no tracking when a user has enabled PII redaction for the server or client. Having this telemetry will help us understand specifically the usage and adoption around the new PII redaction option, and over the long term, give us more insight into which clusters utilize at least one security related feature.

@blathers-crl
Copy link

blathers-crl bot commented Jul 23, 2020

Hi @thtruo, I've guessed the C-ategory of your issue and suitably labeled it. Please re-label if inaccurate.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

@blathers-crl blathers-crl bot added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Jul 23, 2020
@craig craig bot closed this as completed in 620f0a4 Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-security A-telemetry C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants