[
https://issues.apache.org/jira/browse/FLUME-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146770#comment-14146770
]
Jean lagarutte commented on FLUME-2217:
---------------------------------------
hi
i have the same problem.
with flume 1.5 and keepFiels=false, the priority is added to the body.
example :
all my body message begins with <14> text ..... for example
i don't have the problem with flume 1.4
i use log4j 1.2.17.
i don't have the problem with logback because the syslogudp appender results in
: fields.flume.syslog.status = invalid
so it's better with logback sending bad syslog message than log4j sending good
log4j message
what can i do ?
is it possible to retrieve the same behavior as in flume 1.4 ?
> Preserve priority, timestamp and hostname fields in MultiportSyslogTcp and
> Udp sources
> --------------------------------------------------------------------------------------
>
> Key: FLUME-2217
> URL: https://issues.apache.org/jira/browse/FLUME-2217
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.5.0
> Reporter: Jeff Lord
> Assignee: Jeff Lord
> Fix For: v1.5.0
>
> Attachments: FLUME-2217.1.patch, FLUME-2217.2.patch,
> FLUME-2217.3.patch, FLUME-2217.6.patch
>
>
> Flume-1666 added the ability to preserve timestamp and hostname fields of a
> syslog message. We should also add this property to the MultiportSyslogTcp
> Source and the SyslogUdp sources.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
