<?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: Estimating Metric Consumption for Dynatrace SaaS (Network Extension - DPS License) in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Estimating-Metric-Consumption-for-Dynatrace-SaaS-Network/m-p/281091#M37014</link>
    <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/30862"&gt;@AskMe-Solutions&lt;/a&gt;&amp;nbsp;It would be tricky to estimate the license consumption for network devices as it can vary widely based on the metrics ingested and the size/type of network device monitored . If you take an example of a Cisco device , the extension has some details around license calculation which you can use to estimate .&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.dynatrace.com/hub/detail/generic-cisco-router-snmp-extension/" target="_blank"&gt;https://www.dynatrace.com/hub/detail/generic-cisco-router-snmp-extension/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You need to decide on what you would like to monitor on a network device , ie., CPU, Memory , BGP, Interfaces etc., and enable the specific&amp;nbsp;&lt;SPAN&gt;feature sets&amp;nbsp;in the extension to limit the collection of metrics . The extension includes the details of the feature sets that you can enable&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 09 Jul 2025 02:39:02 GMT</pubDate>
    <dc:creator>p_devulapalli</dc:creator>
    <dc:date>2025-07-09T02:39:02Z</dc:date>
    <item>
      <title>Estimating Metric Consumption for Dynatrace SaaS (Network Extension - DPS License)</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Estimating-Metric-Consumption-for-Dynatrace-SaaS-Network/m-p/281051#M37006</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I’m planning to implement &lt;STRONG&gt;Dynatrace SaaS with Extension (DPS License)&lt;/STRONG&gt; to monitor the performance and health of network infrastructure in our organization. Our current device inventory includes:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;F5 R5600&lt;/STRONG&gt;: 4 devices&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Cisco Catalyst 9200 Switches&lt;/STRONG&gt;: 172 devices&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Fortinet 400E&lt;/STRONG&gt;: 2 devices&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Fortinet 200F&lt;/STRONG&gt;: 2 devices&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;VMWare Hosts&lt;/STRONG&gt;: 71 hosts&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We plan to monitor these devices via &lt;STRONG&gt;SNMP, APIs, or vCenter integration&lt;/STRONG&gt;, depending on device compatibility. Metrics will be collected using &lt;STRONG&gt;Extension 2.0&lt;/STRONG&gt; or &lt;STRONG&gt;OneAgent remote plugins&lt;/STRONG&gt;.&lt;/P&gt;&lt;H1&gt;My questions are:&lt;/H1&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Roughly &lt;STRONG&gt;how much DPS (Davis Data Units)&lt;/STRONG&gt; for &lt;STRONG&gt;metric ingest and processing&lt;/STRONG&gt; should we expect to consume &lt;STRONG&gt;per year&lt;/STRONG&gt; for this setup?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Can we &lt;STRONG&gt;customize which metrics&lt;/STRONG&gt; to ingest (e.g., only CPU, Memory, Interface Traffic, Device Health, etc.) to reduce consumption?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Are there any &lt;STRONG&gt;formulas, tools, or best practices&lt;/STRONG&gt; for estimating metric ingestion when using Dynatrace Extensions?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Has anyone here implemented a &lt;STRONG&gt;similar monitoring setup&lt;/STRONG&gt;? If so, could you share your &lt;STRONG&gt;real-world metric consumption&lt;/STRONG&gt; experience?&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Any advice, recommendations, or reference architectures would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 11:11:00 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Estimating-Metric-Consumption-for-Dynatrace-SaaS-Network/m-p/281051#M37006</guid>
      <dc:creator>AskMe-Solutions</dc:creator>
      <dc:date>2025-07-08T11:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: Estimating Metric Consumption for Dynatrace SaaS (Network Extension - DPS License)</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Estimating-Metric-Consumption-for-Dynatrace-SaaS-Network/m-p/281091#M37014</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/30862"&gt;@AskMe-Solutions&lt;/a&gt;&amp;nbsp;It would be tricky to estimate the license consumption for network devices as it can vary widely based on the metrics ingested and the size/type of network device monitored . If you take an example of a Cisco device , the extension has some details around license calculation which you can use to estimate .&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.dynatrace.com/hub/detail/generic-cisco-router-snmp-extension/" target="_blank"&gt;https://www.dynatrace.com/hub/detail/generic-cisco-router-snmp-extension/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You need to decide on what you would like to monitor on a network device , ie., CPU, Memory , BGP, Interfaces etc., and enable the specific&amp;nbsp;&lt;SPAN&gt;feature sets&amp;nbsp;in the extension to limit the collection of metrics . The extension includes the details of the feature sets that you can enable&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jul 2025 02:39:02 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Estimating-Metric-Consumption-for-Dynatrace-SaaS-Network/m-p/281091#M37014</guid>
      <dc:creator>p_devulapalli</dc:creator>
      <dc:date>2025-07-09T02:39:02Z</dc:date>
    </item>
  </channel>
</rss>

