<?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: Network Device topology in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Network-Device-topology/m-p/211635#M26152</link>
    <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/4804"&gt;@y_buccellato&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Topology is included in the SNMP v2 extensions from Dynatrace. Basically, it associates interfaces with the respective devices.&lt;/P&gt;&lt;P&gt;I have not seen yet relationships between a network device and other entities. It would be great if interfaces could de joined/related when they are part of o point-to-point link, as they are in dedicated network monitoring solutions, but most of the times this is done with proprietary solutions, that only work for devices of a certain vendor.&lt;/P&gt;&lt;P&gt;I did see at Perform that a lot of work is being done at the network level. And I believe incorporating this information into the Dynatrace topology model might be something that me be coming in the future...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 08 May 2023 14:57:48 GMT</pubDate>
    <dc:creator>AntonioSousa</dc:creator>
    <dc:date>2023-05-08T14:57:48Z</dc:date>
    <item>
      <title>Network Device topology</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Network-Device-topology/m-p/211594#M26142</link>
      <description>&lt;P&gt;Does Dynatrace maps devices discovered via SNMP extensions on the smartscape topology or service flow?&lt;BR /&gt;Is any relation created between a network device and other entities?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2023 10:11:12 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Network-Device-topology/m-p/211594#M26142</guid>
      <dc:creator>y_buccellato</dc:creator>
      <dc:date>2023-05-08T10:11:12Z</dc:date>
    </item>
    <item>
      <title>Re: Network Device topology</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Network-Device-topology/m-p/211604#M26148</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have never tried it or explore it but looks like a use case for&amp;nbsp;&lt;A title="Custom topology model" href="https://www.dynatrace.com/support/help/shortlink/topology-model" target="_blank" rel="noopener"&gt;Custom topology model&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Best regards&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2023 12:06:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Network-Device-topology/m-p/211604#M26148</guid>
      <dc:creator>AntonPineiro</dc:creator>
      <dc:date>2023-05-08T12:06:17Z</dc:date>
    </item>
    <item>
      <title>Re: Network Device topology</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Network-Device-topology/m-p/211635#M26152</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/4804"&gt;@y_buccellato&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Topology is included in the SNMP v2 extensions from Dynatrace. Basically, it associates interfaces with the respective devices.&lt;/P&gt;&lt;P&gt;I have not seen yet relationships between a network device and other entities. It would be great if interfaces could de joined/related when they are part of o point-to-point link, as they are in dedicated network monitoring solutions, but most of the times this is done with proprietary solutions, that only work for devices of a certain vendor.&lt;/P&gt;&lt;P&gt;I did see at Perform that a lot of work is being done at the network level. And I believe incorporating this information into the Dynatrace topology model might be something that me be coming in the future...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2023 14:57:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Network-Device-topology/m-p/211635#M26152</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2023-05-08T14:57:48Z</dc:date>
    </item>
    <item>
      <title>Re: Network Device topology</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Network-Device-topology/m-p/211675#M26156</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/17213"&gt;@AntonioSousa&lt;/a&gt;&amp;nbsp;relations between entities created using the custom topology model (Extensions 2.0) and built-in entities are not yet present and AFAIK are being worked on. With Custom Devices (Legacy Extenions 1.0) the relations are created based on opaque services and based on IP addresses - a service created on top of the custom device.&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2023 06:44:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Network-Device-topology/m-p/211675#M26156</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2023-05-09T06:44:24Z</dc:date>
    </item>
  </channel>
</rss>

