<?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 Understanding the High CPU Throttling Alert in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Understanding-the-High-CPU-Throttling-Alert/m-p/212515#M3512</link>
    <description>&lt;P&gt;Hello Community.&lt;/P&gt;
&lt;P&gt;I need to understand how this alert is formed.&lt;BR /&gt;I understand that the calculation is the Sum of workload CPU throttled / Sum of workload CPU usage * 100.&lt;/P&gt;
&lt;P&gt;This calculation gives the percentage of throttling that is given from the throttled metric over the CPU usage metric.&lt;BR /&gt;When we turn on this alert, even with a threshold of 100%, we have a lot of alerts going off.&lt;BR /&gt;In analyzing the microservices, we see that these alerts are triggered by specific spikes in CPU throttling/usage.&lt;/P&gt;
&lt;P&gt;The questions that arise for me are as follows:&lt;/P&gt;
&lt;P&gt;1 - How to correctly configure the thresholds to actually alert microservices with high CPU throttling/usage that is sustained over time, and not triggered by specific peaks.&lt;BR /&gt;2 - What recommendations do you give or what documentation is available to further understand how Dynatrace measures and alarms throttling?&lt;/P&gt;
&lt;P&gt;Thank you very much.&lt;/P&gt;
&lt;P&gt;Translated with &lt;A href="http://www.DeepL.com/Translator" target="_blank" rel="noopener"&gt;www.DeepL.com/Translator&lt;/A&gt; (free version)&lt;/P&gt;</description>
    <pubDate>Fri, 26 May 2023 10:54:01 GMT</pubDate>
    <dc:creator>fcalega</dc:creator>
    <dc:date>2023-05-26T10:54:01Z</dc:date>
    <item>
      <title>Understanding the High CPU Throttling Alert</title>
      <link>https://community.dynatrace.com/t5/Alerting/Understanding-the-High-CPU-Throttling-Alert/m-p/212515#M3512</link>
      <description>&lt;P&gt;Hello Community.&lt;/P&gt;
&lt;P&gt;I need to understand how this alert is formed.&lt;BR /&gt;I understand that the calculation is the Sum of workload CPU throttled / Sum of workload CPU usage * 100.&lt;/P&gt;
&lt;P&gt;This calculation gives the percentage of throttling that is given from the throttled metric over the CPU usage metric.&lt;BR /&gt;When we turn on this alert, even with a threshold of 100%, we have a lot of alerts going off.&lt;BR /&gt;In analyzing the microservices, we see that these alerts are triggered by specific spikes in CPU throttling/usage.&lt;/P&gt;
&lt;P&gt;The questions that arise for me are as follows:&lt;/P&gt;
&lt;P&gt;1 - How to correctly configure the thresholds to actually alert microservices with high CPU throttling/usage that is sustained over time, and not triggered by specific peaks.&lt;BR /&gt;2 - What recommendations do you give or what documentation is available to further understand how Dynatrace measures and alarms throttling?&lt;/P&gt;
&lt;P&gt;Thank you very much.&lt;/P&gt;
&lt;P&gt;Translated with &lt;A href="http://www.DeepL.com/Translator" target="_blank" rel="noopener"&gt;www.DeepL.com/Translator&lt;/A&gt; (free version)&lt;/P&gt;</description>
      <pubDate>Fri, 26 May 2023 10:54:01 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Understanding-the-High-CPU-Throttling-Alert/m-p/212515#M3512</guid>
      <dc:creator>fcalega</dc:creator>
      <dc:date>2023-05-26T10:54:01Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding the High CPU Throttling Alert</title>
      <link>https://community.dynatrace.com/t5/Alerting/Understanding-the-High-CPU-Throttling-Alert/m-p/215133#M3579</link>
      <description>&lt;P&gt;you can create a custom threshold that allows you to define the height of the usage for alerting, and you can also create a custom metric event that allows you to define the timeline of alerting. so say alert me when this threshold hits for 6 Mins every hour. Now it wont be a full 6 mins, rather the sum of the mins where the threshold was breached in your 1 hour slot. So, 1 min of high CPU every 10 mins will trigger the alert, even though there are 9 mins in-between each.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 15:58:46 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Understanding-the-High-CPU-Throttling-Alert/m-p/215133#M3579</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2023-06-15T15:58:46Z</dc:date>
    </item>
  </channel>
</rss>

