<?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: Calculated service metrics - Response/Processing time unit in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/168057#M17538</link>
    <description>&lt;P&gt;Hey Babar, yes this has been since the beginning.&lt;/P&gt;</description>
    <pubDate>Mon, 21 Jun 2021 14:09:11 GMT</pubDate>
    <dc:creator>bobby_crumley</dc:creator>
    <dc:date>2021-06-21T14:09:11Z</dc:date>
    <item>
      <title>Calculated service metrics - Response/Processing time unit</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/167564#M17360</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;
&lt;DIV class="gwt-Label"&gt;What could be the reason that the '&lt;STRONG&gt;Response time/Processing time&lt;/STRONG&gt;' unit fixed as '&lt;STRONG&gt;Microsecond&lt;/STRONG&gt;' in the calculated service metrics? Whereas, the same metric can be used with the different units in the c&lt;SPAN&gt;ustom events for alerting.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;The cluster version is&amp;nbsp;&lt;STRONG&gt;1.216.132.20210601-083338&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="gwt-Label"&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="BabarQayyum_0-1623648983200.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/1284i3514526E53FE3AB2/image-size/large?v=v2&amp;amp;px=999" role="button" title="BabarQayyum_0-1623648983200.png" alt="BabarQayyum_0-1623648983200.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Babar&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jun 2021 11:32:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/167564#M17360</guid>
      <dc:creator>Babar_Qayyum</dc:creator>
      <dc:date>2021-06-14T11:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated service metrics - Response/Processing time unit</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/167604#M17377</link>
      <description>&lt;P&gt;Hi Babar&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This metric is captured by Dynatrace in the Microsecond granularity by default, and when reported that can be mathematically grouped and added to show minute/second/millisecond times. As calculated service metrics cannot be adjusted after creation, this ensures the most detailed granularity within this metric so it can be used.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Because of this, this is a metric which can be used for Custom Alerting, and by changing the granularity it just tells the back end to group microseconds into mili/second/minute timings you are requesting.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In short, it prevents a custom metric from creating per minute intervals and trying to make Custom Alerts in second intervals.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jun 2021 18:55:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/167604#M17377</guid>
      <dc:creator>bobby_crumley</dc:creator>
      <dc:date>2021-06-14T18:55:55Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated service metrics - Response/Processing time unit</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/167801#M17414</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/6240"&gt;@bobby_crumley&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your comments. Is this started recently or was it there since the beginning but I did not notice?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Babar&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 18:57:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/167801#M17414</guid>
      <dc:creator>Babar_Qayyum</dc:creator>
      <dc:date>2021-06-17T18:57:21Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated service metrics - Response/Processing time unit</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/168057#M17538</link>
      <description>&lt;P&gt;Hey Babar, yes this has been since the beginning.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jun 2021 14:09:11 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/168057#M17538</guid>
      <dc:creator>bobby_crumley</dc:creator>
      <dc:date>2021-06-21T14:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated service metrics - Response/Processing time unit</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/168072#M17539</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/6240"&gt;@bobby_crumley&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the confirmation.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Babar&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jun 2021 05:58:05 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/168072#M17539</guid>
      <dc:creator>Babar_Qayyum</dc:creator>
      <dc:date>2021-06-22T05:58:05Z</dc:date>
    </item>
    <item>
      <title>Re: Calculated service metrics - Response/Processing time unit</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/188482#M21357</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/6240" target="_blank"&gt;@bobby_crumley&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;BR /&gt;&lt;/SPAN&gt;I want to ask a question here. I want to solve this problem --&amp;gt; alert me when at least 10 request are having response time greater than 10 SECOND in the interval of 5 MINUTES.&amp;nbsp;&lt;BR /&gt;To solve this things, I tried to create calculated service metric for response time when it auto selected to MICROSECOND. Then at the bottom of the page, I selected&lt;STRONG&gt;&amp;nbsp;Response time [ms]&lt;/STRONG&gt; field. Now it is veru confusing should I pass values in MS or MICROSEC here. When I passed as 10000 ms, the alert which was generated considered it as 10 MICROSECOND. So I tried to correct it by passing values as&amp;nbsp;1000000 MICROSEC. But I found that that field doesn't allow any value bigger than&amp;nbsp;&lt;STRONG&gt;1410065&lt;/STRONG&gt;.&lt;BR /&gt;&lt;BR /&gt;So My question to you what should I do here?&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jun 2022 07:02:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Calculated-service-metrics-Response-Processing-time-unit/m-p/188482#M21357</guid>
      <dc:creator>ashish060211</dc:creator>
      <dc:date>2022-06-15T07:02:58Z</dc:date>
    </item>
  </channel>
</rss>

