[FLUME-1938] Flume UDP Source for Windows Events being trimmed at \n characters by SyslogUtils.extractEvent() function

• Type: New Feature
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.3.1
• Component/s: Configuration, Sinks+Sources
• Labels: features patch

Environment

Ubuntu/Linux

Release Note

This feature can be disabled if causes any issues with headers or header extraction process in flume syslog sources (both TCP and UDP).

To enable multi-line configuration set the 'body.multiline' source context configuration to true e.g.

agent.sources.syslogudp.body.multiline=true

• Assignee: Unassigned
• Reporter: Ambud Sharma
• Created: 10/Mar/13 00:02
• Updated: 23/Jun/13 19:54

Description

Flume trims UDP syslog events originating from Kiwi Windows Event Log Forwarder at the first new-line character.

I would like to contribute with a patch to allow configurable inclusion of new-line characters for SyslogUDP source in Flume

Background:
I am using Solarwinds/Kiwi Syslog's Windows Event Log Forwarder. Ref: http://www.solarwinds.com/kiwi-syslog-server.aspx

The Log Forwarder sends CR+LF & horizontal tab characters in the UDP/TCP syslog events that it sends. Other than Kiwi Syslog this problem exists for syslog-ng on certain linux syslog events where CR+LF characters are sent in syslog events.

Syslog-ng handles this problem by replacing these characters with \011 and \015\012 but Flume has no such charset customization available for SyslogUDP. SyslogTCP does have charset customization along with character replace functionality for header.