Debezium connectors log sensitive data (including records keys and values) at various locations throughout the codebase. This creates a challenge for Debezium users who want to enable trace-level logging for debugging purposes while also ensuring that sensitive data is not exposed in the logs. As we lack a central logging approach, user either needs to do local modifications to prevent the sensitive logging or introduce a log-redaction tool to redact the logs. However, with each update from upstream, these changes would need to be re-applied and the existing logs revisited.

As we already have Loggings class to handle sensitive logs, the proposal here is to extend it to the rest of the codebase so as to have a centralised sensitive data logging.

This would streamline the logging process, reduce the risk of exposing sensitive data, and make it easier for users to manage logging configurations without needing to modify the connector or set up separate redaction tools