Is your feature request related to a problem? Please describe.
When the raw_message feature is enabled, in cases that do not use parameterized logging the raw_ message is equal to full_message. This increases the amount of log data, without adding useful information.
This can be a problem when dealing with high log volume but limited resources or quotas defined by support contracts.
Describe the solution you'd like
The GelfEndocer should recognize if a raw_message is actually useful, otherwise skip it.
This should be an optional feature, disabled by default to prevent an API break.
Describe alternatives you've considered
Refactor everything to parameterized logging is basically a good idea, but limited to your own code. Third party libraries may still log without parameters.
If this feature request is considered useful I would provide a PR.
Is your feature request related to a problem? Please describe.
When the
raw_messagefeature is enabled, in cases that do not use parameterized logging theraw_ messageis equal tofull_message. This increases the amount of log data, without adding useful information.This can be a problem when dealing with high log volume but limited resources or quotas defined by support contracts.
Describe the solution you'd like
The
GelfEndocershould recognize if araw_messageis actually useful, otherwise skip it.This should be an optional feature, disabled by default to prevent an API break.
Describe alternatives you've considered
Refactor everything to parameterized logging is basically a good idea, but limited to your own code. Third party libraries may still log without parameters.
If this feature request is considered useful I would provide a PR.