Enhancing Log Masking Granularity for Improved Performance and Flexibility

[cbabey]

Current Limitation

It would be beneficial to enable log masking at a more granular level, such as at the logger, appender, or module level, rather than applying it globally. Currently, multiple log-masking configurations may be necessary for specific services but are not required universally. However, with the existing implementation in the MI, every log event is processed through all configured log-masking rules. This can lead to performance issues, especially under a high logging load from various services.

Logging is often enabled on a per-API and per-service basis, with distinct appenders for each. Some log-masking rules are only relevant to specific APIs, but the current setup does not allow for isolating masking configurations by service, appender, or logger. Instead, the rules are applied globally, impacting all logs, including system logs.

Suggested Improvement

Introducing the flexibility to configure log masking at the logger or appender level could significantly improve efficiency by reducing the overhead of processing each log through all the configured patterns.

Version

No response