Timestamp fails by default, with codec/multiline it works fine
Description
Gliffy Diagrams
Activity
Show:
Jordan Sissel September 13, 2013 at 4:54 PM
Fixed in commit e2faca1
moe lin September 9, 2013 at 8:56 AM
If I understand correctly, stands the wrong value in the timestamp after applying the multiline codec?
Jordan Sissel September 6, 2013 at 3:08 PM
The @timestamp field is intended to always be in UTC/Zulu time. If it ever appears in another time zone, it is a bug.
Can you help me understand what you think is the problem?
I'm form Berlin and i get the wrong timestamp.
The timestamp that i need is
"@timestamp"=>"YYYY-MM-DDTHH:MM:SS.f+02:00"
Fail:
input {stdin { type => "Test" } }
output { stdout { debug => "true" } }
i get -> "@timestamp" => "2013-09-05T09:06:19.578Z"
Works:
input {
stdin {
codec => multiline {
pattern => "^\s"
what => "previous"
}
type => "Test"
}
}
output { stdout { debug => "true" } }
i get -> "@timestamp"=>"2013-09-05T11:02:59.091+02:00"
testet with:
RHEL 6.4 - jdk 1.7.0_25
RHEL 5.9 - jdk 1.7.0_25
CentOS 5.5 - jdk 1.6.0_22