# Aggregate filter does not decorate events that it generates

**URL:** <https://discuss.elastic.co/t/aggregate-filter-does-not-decorate-events-that-it-generates/181662>\
**Category:** Logstash\
**Created:** [May 17, 2019, 9:39pm UTC](https://discuss.elastic.co/t/aggregate-filter-does-not-decorate-events-that-it-generates/181662 "2019-05-17T21:39:06Z")\
**Posts on this page:** 2\
**Page:** 1

<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:** [May 17, 2019, 9:39pm UTC](https://discuss.elastic.co/t/aggregate-filter-does-not-decorate-events-that-it-generates/181662/1 "2019-05-17T21:39:06Z")

</div>

Due to the [noError](https://github.com/logstash-plugins/logstash-filter-aggregate/blob/f3c2ee22d38510b9230eba753ed77e2e16458747/lib/logstash/filters/aggregate.rb#L246) variable, an aggregate filter will only decorate an event (implementing common options like add\_tag) for events that pass through it. Events that it generates (timeouts, final flush) are not decorated. Is that a bug or a feature?

One can work around it by modifying the map prior to it being flushed, or adding the tag in the timeout\_code.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 14, 2019, 9:39pm UTC](https://discuss.elastic.co/t/aggregate-filter-does-not-decorate-events-that-it-generates/181662/2 "2019-06-14T21:39:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.