[
https://issues.apache.org/jira/browse/FLUME-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179685#comment-14179685
]
Benjamin Fiorini commented on FLUME-2512:
-----------------------------------------
As a workaround, because the standard RSYSLOG_ForwardFormat uses microseconds,
I configured rsyslog to truncate the microseconds
{code}$template FLUME_ForwardFormat,
"<%PRI%>%timegenerated:1:23:date-rfc3339%%timegenerated:27:32:date-rfc3339%
%HOSTNAME% %syslogtag%%msg:::sp-if-no-1st-sp%%msg%"{code}
> Support RFC 5424 syslog format timestamp parsing microseconds
> -------------------------------------------------------------
>
> Key: FLUME-2512
> URL: https://issues.apache.org/jira/browse/FLUME-2512
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.4.0
> Reporter: Benjamin Fiorini
>
> Looks like nothing was done for this to support microseconds: FLUME-1126
> In 1.4, the syslog sources do not support microsecond timestamps.
> For instance, this timestamp *2014-10-21T16:40:27.519340+02:00* is parsed to
> *2014-10-21T14:49:06.340Z* (the milliseconds are added as seconds).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
