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
{{ message }}
Repository navigation
parser_syslog: message_format auto parses RFC 3164 messages with an RFC 3339 timestamp as RFC 5424 #5631
It only checks that a digit follows PRI. It does not check the space after VERSION. So an RFC 3164 message whose timestamp starts with the year is detected as RFC 5424. rsyslog's built-in RSYSLOG_ForwardFormat template sends such messages (<%PRI%>%TIMESTAMP:::date-rfc3339% %HOSTNAME% ...). The RFC 5424 parsing then fails, and the parser returns no record.
message_format rfc3164 with time_format parses the same message.
To Reproduce
Run the script below with bundle exec ruby -Ilib repro.rb in this repository.
Results on master (e7d3c3e) for <13>2026-04-25T16:43:29+00:00 web01 nginx: hello:
message_format auto detects this message as RFC 3164 and parses it, as message_format rfc3164 does. For example, the detection could require a space after VERSION.
Your Environment
- Fluentd version: master (e7d3c3e4). v1.20.1 and v1.19.4 have the same code (not run).
- Package version: -
- Operating system: Linux
- Kernel version: -
Your Configuration
<parse>
@type syslog
message_format auto
with_priority true
time_format %Y-%m-%dT%H:%M:%S%z
</parse>
Your Error Log
No error is logged by the parser. It returns no record. (I called the parser directly. in_syslog logs "failed to parse message"for such a result.)
I also reproduced this on v1.19.4 with the same script. The results are the same as on master. REGEXP_DETECT_RFC5424 has had this form since v0.14.14 (b0e9b73).
Activity
Watson1978 commentedon Nov 11, 2026
I also reproduced this on v1.19.4 with the same script. The results are the same as on master.
REGEXP_DETECT_RFC5424has had this form since v0.14.14 (b0e9b73).rafayqayyum commentedon Nov 15, 2026
Opened #5642 for this: the RFC 5424 detection now requires the space after VERSION, so
message_format autoparses your example as RFC 3164.