Priority field is removed from message after syslog parsed #3804
Unanswered
chetaksirsat
asked this question in
Q&A
Replies: 2 comments
-
Hello @chetaksirsat, I know this topic is quiet old but I just found it and I have exactly the same requirements. Regards |
Beta Was this translation helpful? Give feedback.
0 replies
-
@chetaksirsat @subigre If you need to keep |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My fluentd collector today parses syslogs according to our config below but in the process removes the priority field from the message making it a non-compliant RFC format.
BEFORE: Original RFC5424 compliant format message
<99> 1 2022-06-15T11:11:38.313536+00:00 vc vapi-endpoint-access - - - 2022-06-15T11:11:38.313Z | jetty-default-497413 | Invoking operation get from service com.vmware.cis.tagging.tag with id bbfe266d-d31e-4374-9df5-ab261d2bf074
AFTER: Parsed syslog message using Fluentd
1 2022-06-15T11:11:38.313536+00:00 vc vapi-endpoint-access - - - 2022-06-15T11:11:38.313Z | jetty-default-497413 | Invoking operation get from service com.vmware.cis.tagging.tag with id bbfe266d-d31e-4374-9df5-ab261d2bf074
Is there a way to maintain the priority field <99> in the message itself?
Below is the fluentd config -
Beta Was this translation helpful? Give feedback.
All reactions