<?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: How is the response time contribution in service flow being calculated? in Dashboarding</title>
    <link>https://community.dynatrace.com/t5/Dashboarding/How-is-the-response-time-contribution-in-service-flow-being/m-p/64372#M224</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;(Average Response Time) x (Call Percentage) x (Calls per request)&lt;/P&gt;&lt;P&gt;In this case: 288ms * .36*3.5=383ms&lt;/P&gt;&lt;P&gt;Which translates to 14.6% of 2.62s. &lt;/P&gt;&lt;P&gt;There are a couple of rounding errors that happen if you just take the numbers presented here, the 14% is calculated based on the actual underlying data and then rounded off afterwards.&lt;/P&gt;&lt;P&gt;If you click "Filter service flow" on IMOS, the view will filter down to only show requests that do call IMOS, therefore the call percentage will then rise to 100%. This set of request is then a subset of what you look at here, and thus the contribution will be higher, cause it contributes to every request in that new picture.&lt;/P&gt;&lt;P&gt;I hope this explains it.&lt;/P&gt;&lt;P&gt;Best&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;</description>
    <pubDate>Tue, 17 Apr 2018 09:40:25 GMT</pubDate>
    <dc:creator>michael_kopp</dc:creator>
    <dc:date>2018-04-17T09:40:25Z</dc:date>
    <item>
      <title>How is the response time contribution in service flow being calculated?</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/How-is-the-response-time-contribution-in-service-flow-being/m-p/64371#M223</link>
      <description>&lt;P&gt;I have looked at all the figures in the service flow dashboard, but couldn't find a way to get the number displayed as response time contribution percentage.&lt;/P&gt;
&lt;P&gt;Does anyone know how's the calculation is being done?&lt;/P&gt;
&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/16532-response-time-contribution-in-service-flow.png" border="0" /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jan 2022 08:52:44 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/How-is-the-response-time-contribution-in-service-flow-being/m-p/64371#M223</guid>
      <dc:creator>waikeat_chan</dc:creator>
      <dc:date>2022-01-12T08:52:44Z</dc:date>
    </item>
    <item>
      <title>Re: How is the response time contribution in service flow being calculated?</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/How-is-the-response-time-contribution-in-service-flow-being/m-p/64372#M224</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;(Average Response Time) x (Call Percentage) x (Calls per request)&lt;/P&gt;&lt;P&gt;In this case: 288ms * .36*3.5=383ms&lt;/P&gt;&lt;P&gt;Which translates to 14.6% of 2.62s. &lt;/P&gt;&lt;P&gt;There are a couple of rounding errors that happen if you just take the numbers presented here, the 14% is calculated based on the actual underlying data and then rounded off afterwards.&lt;/P&gt;&lt;P&gt;If you click "Filter service flow" on IMOS, the view will filter down to only show requests that do call IMOS, therefore the call percentage will then rise to 100%. This set of request is then a subset of what you look at here, and thus the contribution will be higher, cause it contributes to every request in that new picture.&lt;/P&gt;&lt;P&gt;I hope this explains it.&lt;/P&gt;&lt;P&gt;Best&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;</description>
      <pubDate>Tue, 17 Apr 2018 09:40:25 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/How-is-the-response-time-contribution-in-service-flow-being/m-p/64372#M224</guid>
      <dc:creator>michael_kopp</dc:creator>
      <dc:date>2018-04-17T09:40:25Z</dc:date>
    </item>
  </channel>
</rss>

