# LOG 2.0: Log events merged

**URL:** <https://community.dynatrace.com/t/log-2-0-log-events-merged/35688>\
**Category:** Logs\
**Tags:** log-monitoring-class\
**Created:** [June 30, 2022, 12:28pm UTC](https://community.dynatrace.com/t/log-2-0-log-events-merged/35688 "2022-06-30T12:28:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rastislav\_danis](https://avatars.discourse-cdn.com/v4/letter/r/b9bd4f/32.png) [@rastislav\_danis](https://community.dynatrace.com/u/rastislav_danis)\
**Post date:** [June 30, 2022, 12:28pm UTC](https://community.dynatrace.com/t/log-2-0-log-events-merged/35688/1 "2022-06-30T12:28:59Z")

</div>

Custom log event definition has “Allow merge” checked. At same time 3 various log messages are generated and catched by mentioned custom log event’s Log query. Problem generated by this custom log event contains ONLY last (top one, when looking into log via Dynatrace Log GUI) of 3 messages. Is this an expected behaviour of “Merge” action ?

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [March 10, 2023, 6:18pm UTC](https://community.dynatrace.com/t/log-2-0-log-events-merged/35688/2 "2023-03-10T18:18:14Z")

</div>

[@rastislav\_danis](https://community.dynatrace.com/user/38440)&nbsp;has this been fixed in your cluster? It might also be resolved in GRAIL as well. let us know on the status of the issue 🙂

---

<div class="post-metadata">

**Author:** ![rastislav\_danis](https://avatars.discourse-cdn.com/v4/letter/r/b9bd4f/32.png) [@rastislav\_danis](https://community.dynatrace.com/u/rastislav_danis)\
**Post date:** [March 13, 2023, 8:27am UTC](https://community.dynatrace.com/t/log-2-0-log-events-merged/35688/3 "2023-03-13T08:27:37Z")

</div>

In this case 3 lines we treated as different were in fact the same. 😉 Combination of specific log entry properties constructs uniqueness of event (i cannot remember exactly which ones actually). One common detection rule was used originally, solution for this issue was to detect specific log entries in separate detection rules.
