You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Vinayaka Ramachandra (JIRA)" <ji...@apache.org> on 2015/01/22 05:53:34 UTC
[jira] [Created] (LOG4J2-944) Log4j Flume appender is not adding
millisecond to the event headers when the event is logged at 000
milliseconds.
Vinayaka Ramachandra created LOG4J2-944:
-------------------------------------------
Summary: Log4j Flume appender is not adding millisecond to the event headers when the event is logged at 000 milliseconds.
Key: LOG4J2-944
URL: https://issues.apache.org/jira/browse/LOG4J2-944
Project: Log4j 2
Issue Type: Bug
Components: Flume Appender
Affects Versions: 2.0-rc1
Reporter: Vinayaka Ramachandra
If the event happens at exact 000 milliseconds, then milliseconds is not inserted.
We are sending the data to Flume appenders in syslog Format. where it will add headers. In header the standard time stamp is in Below Format
2015-01-06T07:32:43.345-08:00
But when the event is logged exactly at 000 milliseconds then millisecond part is missing as we can see in below code.
2015-01-06T07:32:43-08:00
This cause exception when we process the data including milliseconds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org