# Logs not in sequence as in console output

**URL:** https://discuss.elastic.co/t/logs-not-in-sequence-as-in-console-output/188437
**Category:** Logstash
**Created:** [July 2, 2019, 6:08am UTC](https://discuss.elastic.co/t/logs-not-in-sequence-as-in-console-output/188437 "2019-07-02T06:08:31Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [July 2, 2019, 12:44pm UTC](https://discuss.elastic.co/t/logs-not-in-sequence-as-in-console-output/188437/5 "2019-07-02T12:44:00Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> I am not sure if the ordering of events is guaranteed once you get to the filter stage

With the java execution engine (the default in v7) both filters and outputs [can](https://discuss.elastic.co/t/elpased-filter-works-differently-6-8-1-vs-7-1-possible-bug/187400/2) re-order events, even with '--pipeline.workers 1'.

---

_[View the full topic](https://discuss.elastic.co/t/logs-not-in-sequence-as-in-console-output/188437)._