Repository navigation
Make LoggingEventEnhancer more generic so can be used in more implementations #32
Description
Activity
Thank you for your proposal. Indeed it enhances the abilities to customize the published logs by introducing a common logic across the application. We consider this change to be a breaking change. It cannot be implemented without either creating a flow that duplicates the existing method or by changing the existing
LoggingEnhancerinterface. It means this change can be introduced only within the next major release.
Please, see if the next release (probably 3.6) that introducing automatic metadata population helps you with some of the tasks for automatic log entry enhancement. See PR #808 for more details.I am closing this issue since seems it is pretty old and apparently seems there is no much demand for this feature - please let me know if anyone thinks otherwise
Is your feature request related to a problem? Please describe.
Currently only
com.google.cloud.logging.logback.LoggingAppendercan enhance using information contained within the logging event. This isn't possible via the JDK logger although it should be.Describe the solution you'd like
Replace
com.google.cloud.logging.logback.LoggingEventEnhancerwithcom.google.cloud.logging.LoggingEventEnhancerthat has a class structure similar to:For backwards compatibility
com.google.cloud.logging.logback.LoggingEventEnhancercould then change to:Describe alternatives you've considered
None
Additional context
The JDK logger
com.google.cloud.logging.LoggingHandlershould then be enhanced to perform the enhancement using the new class. The oldcom.google.cloud.logging.LoggingEnhancercould be deprecated as its functionality could be subsumed by the new one.