Hi,
I've got a logstash pipeline taking events from a HTTP poller input to an ES output, configured with persistent queue. The incoming events do not contain an @timestamp field, and we don't add one at any point in the pipeline.
My understanding, based mainly on comment by @magnusbaeck here Add field timestamp with current time - is that the @timestamp field is being added at the input plugin. However, we recently had an issue where ES was offline for a number of hours and as a result the events built up on the persistent queue. When ES was back on-line, all of the events from the intervening period were pushed through as expected, but they all went into ES with the timestamp set to current time, rather than the expected behaviour of the timestamp being the time at which the HTTP poller had obtained the events from source.
So my question is am I correctly understanding the expected behaviour, and if so, is this a general logstash issue, or an issue specific to the http poller input? Thanks!
- Adrian