Add Credit Card Numbers to Data Security Page #30579
Open
+106
−56
Conversation
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
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
|
@ajgajg1134 - Hello! Looks like you had written the internal docs for this content. When you have a sec, could you please verify my additions? Thanks! |
brett0000FF
changed the title
Preview links (active after the
|
michaelcretzman
approved these changes
Jul 18, 2025
|
|
||
| Scans all span metadata for numbers that appear to be credit card numbers. Any values that match are replaced with `?`. This check affects all span types and is enabled by default. | ||
|
|
||
| **Note**: Scanning looks for values that are exactly credit card numbers (allowing for internal whitespace). If a meta value has additional string data, this obfuscator considers that value to not be a credit card number. For example: |
There was a problem hiding this comment.
Suggested change
| **Note**: Scanning looks for values that are exactly credit card numbers (allowing for internal whitespace). If a meta value has additional string data, this obfuscator considers that value to not be a credit card number. For example: | |
| **Note**: Scanning looks for values that are exactly credit card numbers (allowing for internal whitespace). If a metavalue has additional string data, this obfuscator determine that value is not a credit card number. For example: |
Comment on lines
+428
to
+429
| - A meta value of `4111 1111 1111 1111` is redacted to `?`. | ||
| - A meta value of `CC-4111 1111 1111 1111` is **not** redacted. |
There was a problem hiding this comment.
Suggested change
| - A meta value of `4111 1111 1111 1111` is redacted to `?`. | |
| - A meta value of `CC-4111 1111 1111 1111` is **not** redacted. | |
| - A metavalue of `4111 1111 1111 1111` is redacted to `?`. | |
| - A metavalue of `CC-4111 1111 1111 1111` is **not** redacted. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR do? What is the motivation?
This undocumented feature automatically detects and redacts Primary Account Numbers (PANs) found in trace metadata across all programming languages.
The documentation now includes:
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes