<?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: Dynatrace Managed hardware for supporting mainframe monitoring in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-hardware-for-supporting-mainframe-monitoring/m-p/126074#M994</link>
    <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/47741"&gt;@jose&lt;/a&gt; L. After working with support on this to ensure you get the correct answer to your questions, It would be advised to follow the following guidelines as to how much that node size can compute.&lt;/P&gt;
&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/22926-node-loads.png" border="0" /&gt;&lt;/P&gt;
&lt;P&gt;The full link to where this image was captured from: &lt;A href="https://docs.dynatrace.com/managed/shortlink/managed-requirements" target="_self"&gt;Managed hardware requirements&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Its better to be bigger then needed rather then smaller as you will see adverse affects. However, keeping this in mind everyone's environment is different and might have added costs from a resources standpoint.&lt;/P&gt;
&lt;P&gt;If you feel that this answer is a Quality Answer to your question, please feel free to mark it as the "Best Answer" as well as reward the user who provided it by clicking "Reward User"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 13 Mar 2025 07:59:47 GMT</pubDate>
    <dc:creator>ctturner</dc:creator>
    <dc:date>2025-03-13T07:59:47Z</dc:date>
    <item>
      <title>Dynatrace Managed hardware for supporting mainframe monitoring</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-hardware-for-supporting-mainframe-monitoring/m-p/126072#M992</link>
      <description>&lt;P&gt;Hello. I realize that there a public page where is detailed cluster sizing for Dynatrace managed hardware according to number of hosts to be monitored.&lt;/P&gt;
&lt;P&gt;In the case of a Mainframe (z/OS) monitoring, are there any Dynatrace managed hardware sizing guidelines ?&lt;/P&gt;
&lt;P&gt;Many Thanks!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Apr 2023 09:33:07 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-hardware-for-supporting-mainframe-monitoring/m-p/126072#M992</guid>
      <dc:creator>jose_damian_rui</dc:creator>
      <dc:date>2023-04-13T09:33:07Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Managed hardware for supporting mainframe monitoring</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-hardware-for-supporting-mainframe-monitoring/m-p/126073#M993</link>
      <description>&lt;P&gt;You have to use these guidelines:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.dynatrace.com/managed/shortlink/managed-requirements" target="_self"&gt;Managed hardware requirements&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;everything depends of number of hosts and the amount of traffic you expect to have. You may as well consider using more than one cluster if you want to have redundance of data.&lt;/P&gt;
&lt;P&gt;Sebastian&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Mar 2025 07:59:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-hardware-for-supporting-mainframe-monitoring/m-p/126073#M993</guid>
      <dc:creator>skrystosik</dc:creator>
      <dc:date>2025-03-13T07:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Managed hardware for supporting mainframe monitoring</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-hardware-for-supporting-mainframe-monitoring/m-p/126074#M994</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/47741"&gt;@jose&lt;/a&gt; L. After working with support on this to ensure you get the correct answer to your questions, It would be advised to follow the following guidelines as to how much that node size can compute.&lt;/P&gt;
&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/22926-node-loads.png" border="0" /&gt;&lt;/P&gt;
&lt;P&gt;The full link to where this image was captured from: &lt;A href="https://docs.dynatrace.com/managed/shortlink/managed-requirements" target="_self"&gt;Managed hardware requirements&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Its better to be bigger then needed rather then smaller as you will see adverse affects. However, keeping this in mind everyone's environment is different and might have added costs from a resources standpoint.&lt;/P&gt;
&lt;P&gt;If you feel that this answer is a Quality Answer to your question, please feel free to mark it as the "Best Answer" as well as reward the user who provided it by clicking "Reward User"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Mar 2025 07:59:47 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-hardware-for-supporting-mainframe-monitoring/m-p/126074#M994</guid>
      <dc:creator>ctturner</dc:creator>
      <dc:date>2025-03-13T07:59:47Z</dc:date>
    </item>
  </channel>
</rss>

