<?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: Problem root cause always &amp;quot;1&amp;quot; entity? in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Problem-root-cause-always-quot-1-quot-entity/m-p/276431#M5620</link>
    <description>&lt;P&gt;Hi Chad,&lt;/P&gt;&lt;P&gt;It is just a field in the problem record:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="henk_stobbe_0-1746262359671.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/27838iFE0BDACD97E8709C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="henk_stobbe_0-1746262359671.png" alt="henk_stobbe_0-1746262359671.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;KR Henk&lt;/P&gt;</description>
    <pubDate>Sat, 03 May 2025 08:52:58 GMT</pubDate>
    <dc:creator>henk_stobbe</dc:creator>
    <dc:date>2025-05-03T08:52:58Z</dc:date>
    <item>
      <title>Problem root cause always "1" entity?</title>
      <link>https://community.dynatrace.com/t5/Alerting/Problem-root-cause-always-quot-1-quot-entity/m-p/267086#M5373</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Reading the documentation:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;A problem might result from single or &lt;U&gt;&lt;EM&gt;&lt;STRONG&gt;multiple events&lt;/STRONG&gt; &lt;/EM&gt;&lt;/U&gt;occurring simultaneously within the same topology.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;But looking the events there in a field: "root_cause_entity_id" and this is not an array.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So should the documentation be changed to:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;A problem might result from single or &lt;U&gt;&lt;EM&gt;&lt;STRONG&gt;multiple events&lt;/STRONG&gt; &lt;/EM&gt;&lt;/U&gt;occurring simultaneously within the same topology &lt;U&gt;&lt;EM&gt;&lt;STRONG&gt;from the same source entity&lt;/STRONG&gt;&lt;/EM&gt;&lt;/U&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Who can shed some light the matter?&lt;/P&gt;&lt;P&gt;KR Henk&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 13:58:59 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Problem-root-cause-always-quot-1-quot-entity/m-p/267086#M5373</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2025-01-10T13:58:59Z</dc:date>
    </item>
    <item>
      <title>Re: Problem root cause always "1" entity?</title>
      <link>https://community.dynatrace.com/t5/Alerting/Problem-root-cause-always-quot-1-quot-entity/m-p/276419#M5619</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/11427"&gt;@henk_stobbe&lt;/a&gt;&amp;nbsp;- the&amp;nbsp;&lt;SPAN&gt;"root_cause_entity_id" im assuming is coming from the problem card Json, what does it have for a problem card where there are multiple impacted entities which also might then have multiple root causes?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 02 May 2025 19:35:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Problem-root-cause-always-quot-1-quot-entity/m-p/276419#M5619</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2025-05-02T19:35:48Z</dc:date>
    </item>
    <item>
      <title>Re: Problem root cause always "1" entity?</title>
      <link>https://community.dynatrace.com/t5/Alerting/Problem-root-cause-always-quot-1-quot-entity/m-p/276431#M5620</link>
      <description>&lt;P&gt;Hi Chad,&lt;/P&gt;&lt;P&gt;It is just a field in the problem record:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="henk_stobbe_0-1746262359671.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/27838iFE0BDACD97E8709C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="henk_stobbe_0-1746262359671.png" alt="henk_stobbe_0-1746262359671.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;KR Henk&lt;/P&gt;</description>
      <pubDate>Sat, 03 May 2025 08:52:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Problem-root-cause-always-quot-1-quot-entity/m-p/276431#M5620</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2025-05-03T08:52:58Z</dc:date>
    </item>
    <item>
      <title>Re: Problem root cause always "1" entity?</title>
      <link>https://community.dynatrace.com/t5/Alerting/Problem-root-cause-always-quot-1-quot-entity/m-p/277891#M5663</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/11427"&gt;@henk_stobbe&lt;/a&gt;! Thanks for your feedback. The docs team is on it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 May 2025 07:16:28 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Problem-root-cause-always-quot-1-quot-entity/m-p/277891#M5663</guid>
      <dc:creator>GosiaMurawska</dc:creator>
      <dc:date>2025-05-23T07:16:28Z</dc:date>
    </item>
  </channel>
</rss>

