# Aggregate and elapsed filter plugins - multiple events processing
**URL:** https://discuss.elastic.co/t/aggregate-and-elapsed-filter-plugins-multiple-events-processing/78573
**Category:** Logstash
**Created:** [March 14, 2017, 5:58pm UTC](https://discuss.elastic.co/t/aggregate-and-elapsed-filter-plugins-multiple-events-processing/78573 "2017-03-14T17:58:18Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Nikolay\_Shushkin](https://discuss.elastic.co/u/Nikolay_Shushkin)
#### Post date: [March 14, 2017, 5:58pm UTC](https://discuss.elastic.co/t/aggregate-and-elapsed-filter-plugins-multiple-events-processing/78573/1 "2017-03-14T17:58:18Z")
Why there is a limitation in **aggregate** plugin usage:
"`You should be very careful to set logstash filter workers to 1 (-w 1 flag) for this filter to work correctly otherwise events may be processed out of sequence and unexpected results will occur`".
But another filter plugin **elapsed** which works with multiple events too does not have such a limitation?
It seems that "out of sequence processing" effect is more important in duration calculation but not in aggregation.
---
### Author:  [@whyapenny](https://discuss.elastic.co/u/whyapenny)
#### Post date: [March 16, 2017, 4:44am UTC](https://discuss.elastic.co/t/aggregate-and-elapsed-filter-plugins-multiple-events-processing/78573/2 "2017-03-16T04:44:56Z")
i believe elapsed filter, too, has such limitation. If processed out of sequence, elapsed filter will throw an error for an event with no beginning.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 13, 2017, 4:45am UTC](https://discuss.elastic.co/t/aggregate-and-elapsed-filter-plugins-multiple-events-processing/78573/3 "2017-04-13T04:45:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.