<?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: Can Dynatrace in its &amp;quot;Problem analysis&amp;quot; point to the network device as a root cause of the problem? in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Can-Dynatrace-in-its-quot-Problem-analysis-quot-point-to-the/m-p/213188#M26507</link>
    <description>&lt;P&gt;it should be able to if you can onboard those entities. Here is a sample of a network anomaly and how it was detected, granted its at a process group level but I imagine it could apply to your onboarded network component.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ChadTurner_1-1685039948561.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/11884i7F3987F276D2A77B/image-size/large?v=v2&amp;amp;px=999" role="button" title="ChadTurner_1-1685039948561.png" alt="ChadTurner_1-1685039948561.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 25 May 2023 18:39:21 GMT</pubDate>
    <dc:creator>ChadTurner</dc:creator>
    <dc:date>2023-05-25T18:39:21Z</dc:date>
    <item>
      <title>Can Dynatrace in its "Problem analysis" point to the network device as a root cause of the problem?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Can-Dynatrace-in-its-quot-Problem-analysis-quot-point-to-the/m-p/207121#M25166</link>
      <description>&lt;P&gt;I have a client who wants to onboard Cisco routers and Juniper network devices.&lt;/P&gt;
&lt;P&gt;The question is, can Dynatrace in its Problem analysis point to the network device as a root cause of the problem?&lt;/P&gt;
&lt;P&gt;Could I get share a screenshot where this is possible on the problems page?&lt;/P&gt;</description>
      <pubDate>Mon, 20 Mar 2023 14:39:15 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Can-Dynatrace-in-its-quot-Problem-analysis-quot-point-to-the/m-p/207121#M25166</guid>
      <dc:creator>echwallah</dc:creator>
      <dc:date>2023-03-20T14:39:15Z</dc:date>
    </item>
    <item>
      <title>Re: Can Dynatrace in its "Problem analysis" point to the network device as a root cause of the problem?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Can-Dynatrace-in-its-quot-Problem-analysis-quot-point-to-the/m-p/213188#M26507</link>
      <description>&lt;P&gt;it should be able to if you can onboard those entities. Here is a sample of a network anomaly and how it was detected, granted its at a process group level but I imagine it could apply to your onboarded network component.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ChadTurner_1-1685039948561.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/11884i7F3987F276D2A77B/image-size/large?v=v2&amp;amp;px=999" role="button" title="ChadTurner_1-1685039948561.png" alt="ChadTurner_1-1685039948561.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2023 18:39:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Can-Dynatrace-in-its-quot-Problem-analysis-quot-point-to-the/m-p/213188#M26507</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2023-05-25T18:39:21Z</dc:date>
    </item>
  </channel>
</rss>

