Redacted registry memory mapping in crash tracking#11025
Open
Redacted registry memory mapping in crash tracking#11025
Conversation
bric3
added
type: enhancement
bric3
force-pushed
the
bdu/register-mappings
branch
from
1fa1dbd to
b8ae4df
Compare
bric3
force-pushed
the
bdu/register-mappings
branch
from
b7c2fd7 to
c71deb4
Compare
bric3
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Does This Do
This pull request enhances crash tracking by implementing the following features:
Note
This PR introduced the
dd.crashtracking.experimental.register-mapping.enabledconfig key, but given #11048 has a wider config, this will be migrated to the new key.Motivation
To improve debugging capabilities and ensure sensitive information is not exposed during crash reporting.
Additional Notes
The redaction util is specific to the crashtracking because the shape of the data is not exactly the same.