-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Collect additional telemetry for crypto/runtime errors #7394
Conversation
tnorling
commented
Oct 22, 2024
- Adds additional check for the subtle property on crypto
- Fixes error stack logic to keep top 5 lines instead of bottom 5
- Collects common, known runtime errors and redacts when necessary
) { | ||
const line = stackArr[ix]; | ||
// These types of errors are not at risk of leaking PII. They will indicate unavailable APIs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we guarantee this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, these are thrown when we call an API or access an object property that doesn't exist, neither of which are PII and we control this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*can we get a guidance to the team so folks don't accidentally add PII?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm saying there's not a risk of that. APIs and object properties are not PII