You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current upstream version 3.0.5 has the following code in the register function:
if@codec.instance_of?LogStash::Codecs::Plainend
which always returns false and so the @format of the LogStash::Codecs::Plain codec is never defined, making the message config option of the plugin useless as it's always with the default value %{message}.
Further, since there is no @format defined for LogStash::Codecs::Plain, the encode function of the codec always relies on event.to_s which results in syslog actual payload becoming %{timestamp} %{host} %{message}. And, this is always prepending the %{timestamp} %{host} part which breaks the format of the desired syslog payload.
I'm using this plugin to send high volume logs to our other critical systems that use the messages received via syslog to identify various kinds of patterns in the logs. It would make our work easier and would benefit everyone if the current changes are pushed to the upstream with a new patch version. Thanks
The text was updated successfully, but these errors were encountered:
The current upstream version 3.0.5 has the following code in the
register
function:which always returns false and so the
@format
of theLogStash::Codecs::Plain
codec is never defined, making themessage
config option of the plugin useless as it's always with the default value%{message}
.Further, since there is no
@format
defined forLogStash::Codecs::Plain
, theencode
function of the codec always relies onevent.to_s
which results in syslog actual payload becoming%{timestamp} %{host} %{message}
. And, this is always prepending the%{timestamp} %{host}
part which breaks the format of the desired syslog payload.I'm using this plugin to send high volume logs to our other critical systems that use the messages received via syslog to identify various kinds of patterns in the logs. It would make our work easier and would benefit everyone if the current changes are pushed to the upstream with a new patch version. Thanks
The text was updated successfully, but these errors were encountered: