As you can see in message date = 2015.11.10 03:02:34.988. But in @timestamp I have "2015-11-09T21:02:34.988Z". Why it is not equal?
The @timestamp field is UTC while the time displayed in the browser is adjusted to the browser's local time. The six-hour difference between your two timestamps are explained by the UTC+6 timezone in Novosibirsk.
Message field has been corrupted(( Full message may look loke: "Event was changed for Id 194. Old value was null, new value is 67"
It looks like the original message actually was " at b.a()", seemingly a line from a multiline stacktrace.
My logs have this record: "2015.11.10 03:07:57.523: Thread was being aborted. , at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)
at System.Threading.Thread.Sleep(Int32 millisecondsTimeout)
at b.a()"
When I create simple " * " index, Kibana shows all 1000+ logs normally including the above record.
Problems starts when I trying create . common-logs-* index. In that case it only shows 4 logs from 1000.
If I don't use a date plugin - Kibana shows everything correctly/
I strongly doubt the date filter has anything to do with this. I don't know what you mean by "* index". Lines without a timestamp in the beginning will be stamped with the current date and time, so if you're processing old logs they will be found in the wrong place.
Instead of focusing on thousands of events, feed Logstash with a single line and make sure you get the expected results.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.