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

Expand PII scrubbing to all Error telemetry fields #14158

Open
danielayala94 opened this issue Dec 3, 2024 · 0 comments · May be fixed by #14161
Open

Expand PII scrubbing to all Error telemetry fields #14158

danielayala94 opened this issue Dec 3, 2024 · 0 comments · May be fixed by #14161
Assignees
Milestone

Comments

@danielayala94
Copy link
Contributor

danielayala94 commented Dec 3, 2024

Problem Description

Some fields in Error telemetry instances are not processed for removed PII.

For instance, call stacks are correctly processed to remove PII from file paths, but other fields can potentially include such information and are not being processed yet.

Steps To Reproduce

N/A

Expected Results

PII scrubbing should occur for all Error telemetry fields.

CLI version

N/A

Environment

N/A

Community Modules

No response

Target Platform Version

None

Target Device(s)

No response

Visual Studio Version

None

Build Configuration

None

Snack, code example, screenshot, or link to a repository

No response

@danielayala94 danielayala94 self-assigned this Dec 3, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Invalid Triage https://github.com/microsoft/react-native-windows/wiki/Triage-Process (label applied by bot) label Dec 4, 2024
@chrisglein chrisglein added this to the Next milestone Dec 18, 2024
@danielayala94 danielayala94 removed the Invalid Triage https://github.com/microsoft/react-native-windows/wiki/Triage-Process (label applied by bot) label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants