Skip to content

Commit bdfa763

Browse files
committed
in_syslog: Add FAQ for non-RFC3164/RFC5424 message
Signed-off-by: Masahiro Nakagawa <repeatedly@gmail.com>
1 parent 114446a commit bdfa763

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

plugins/input/syslog.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -404,6 +404,22 @@ With this configuration, 3 workers share 5140 port. No need additional
404404
port. Incoming data will be routed to 3 workers automatically.
405405

406406

407+
## FAQ
408+
409+
### Our system sends RFC3164/RFC5424 message but parse failure happens
410+
411+
First, check your message format follows RFC3164/RFC5424 or not.
412+
Some systems say RFC3164/RFC5424 but it sends non-RFC3164/RFC5424 message, e.g. invalid priority, different timestamp, lack/add fields.
413+
414+
If only timestamp is different, configure `time_format` in `<parse>` may help.
415+
416+
If other parts are different, syslog parser can't parse your message.
417+
To resolve the problem, there are several approaches:
418+
419+
- Use regex parser or write your parser
420+
- Use in_udp/in_tcp with other parsers
421+
422+
407423
## Learn More
408424

409425
- [Input Plugin Overview](/plugins/input/README.md)

0 commit comments

Comments
 (0)