Description of problem: In order to protect sensitive data in accordance with regulation, compliance, and corporate policy log masking should be available. Specified variables should be automatically masked when logged. Version-Release number of selected component (if applicable): None How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Logs are viewable as plain text. Expected results: Specified variables in the logs should not be viewable as plain text. Additional info:
Jeremy, What types of items are being requested here to be masked? Are you requesting that this be a configurable filter on logging (which I don't think is possible without significant changes to the log package)?
Paul, I am requesting a filter. The customer needs a way to mask values logged from the application, for example, social security numbers or patient names. I don't think it would have to be too configurable.
@Tushar, Revisiting the backlog during grooming. Why is this the responsibility of the logging stack and not the application that generates the logs? If the information is so sensitive that it shouldn't be visible, then the application which writes the information should be responsible IMO
@Jeremy - same question as above - why would logging be special in this regard? Once the data is emitted by the application, it is fair game for everyone, not just logging.
Closing in favor of https://jira.coreos.com/browse/LOG-49