-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[processor/redaction] Add Support for Redacting log.body in the Redaction Processor #37239
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
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I agree that the body is a logical field for this component to comprehend |
Hi @karakayasemi , I would like to work on this if possible. As I can see, we want to add something like a |
Yes, you can work on this if you are available. We can extend the existing |
@akstron I have already submitted a PR, feel free to add any comment. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
## Description This update applies redaction rules to the `log.body` field by supporting multiple data types, including string, slices, maps, and nested maps. It applies key-based configurations consistently across all map structures. - **Key-Based Configurations**: Applies redaction rules at all nesting levels. - **New Debug Attributes**: - `redaction.body.redacted.keys` / `redaction.body.redacted.count` - `redaction.body.masked.keys` / `redaction.body.masked.count` - `redaction.body.allowed.keys` / `redaction.body.allowed.count` - `redaction.body.ignored.count` #### Link to tracking issue Fixes #37239 ## Testing & Refactoring - **Extended Tests**: Log body redaction added to all existing cases + new tests for detailed body structure validation. - **Code Cleanup**: Introduced helper methods for redaction, masking, allowing, and ignoring logic. - **Improved Readability**: Renamed some const variables for clarity and consistency. --------- Co-authored-by: Antoine Toulme <[email protected]>
…) (open-telemetry#37369) ## Description This update applies redaction rules to the `log.body` field by supporting multiple data types, including string, slices, maps, and nested maps. It applies key-based configurations consistently across all map structures. - **Key-Based Configurations**: Applies redaction rules at all nesting levels. - **New Debug Attributes**: - `redaction.body.redacted.keys` / `redaction.body.redacted.count` - `redaction.body.masked.keys` / `redaction.body.masked.count` - `redaction.body.allowed.keys` / `redaction.body.allowed.count` - `redaction.body.ignored.count` #### Link to tracking issue Fixes open-telemetry#37239 ## Testing & Refactoring - **Extended Tests**: Log body redaction added to all existing cases + new tests for detailed body structure validation. - **Code Cleanup**: Introduced helper methods for redaction, masking, allowing, and ignoring logic. - **Improved Readability**: Renamed some const variables for clarity and consistency. --------- Co-authored-by: Antoine Toulme <[email protected]>
Component(s)
processor/redaction
Is your feature request related to a problem? Please describe.
The redaction processor currently supports redacting attributes. However, sensitive data often resides in
log.body,
where user-generated messages or critical information is logged.Describe the solution you'd like
Add support for redacting
log.body
in the redaction processor.Describe alternatives you've considered
No response
Additional context
If this proposal makes sense to the community, I am willing to contribute to the implementation as a feature PR.
The text was updated successfully, but these errors were encountered: