<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: LOG 2.0: Log events merged in Log Analytics</title>
    <link>https://community.dynatrace.com/t5/Log-Analytics/LOG-2-0-Log-events-merged/m-p/206861#M532</link>
    <description>&lt;P&gt;In this case 3 lines we treated as different were in fact the same. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; 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.&lt;/P&gt;</description>
    <pubDate>Mon, 13 Mar 2023 08:27:37 GMT</pubDate>
    <dc:creator>rastislav_danis</dc:creator>
    <dc:date>2023-03-13T08:27:37Z</dc:date>
    <item>
      <title>LOG 2.0: Log events merged</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/LOG-2-0-Log-events-merged/m-p/189593#M530</link>
      <description>&lt;P&gt;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 ?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2022 12:30:29 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/LOG-2-0-Log-events-merged/m-p/189593#M530</guid>
      <dc:creator>rastislav_danis</dc:creator>
      <dc:date>2022-06-30T12:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: LOG 2.0: Log events merged</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/LOG-2-0-Log-events-merged/m-p/206806#M531</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/38440"&gt;@rastislav_danis&lt;/a&gt;&amp;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 &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 18:18:14 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/LOG-2-0-Log-events-merged/m-p/206806#M531</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2023-03-10T18:18:14Z</dc:date>
    </item>
    <item>
      <title>Re: LOG 2.0: Log events merged</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/LOG-2-0-Log-events-merged/m-p/206861#M532</link>
      <description>&lt;P&gt;In this case 3 lines we treated as different were in fact the same. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; 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.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Mar 2023 08:27:37 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/LOG-2-0-Log-events-merged/m-p/206861#M532</guid>
      <dc:creator>rastislav_danis</dc:creator>
      <dc:date>2023-03-13T08:27:37Z</dc:date>
    </item>
  </channel>
</rss>

