# Service flow -  Calculation of the Response time contribution metric

**URL:** <https://community.dynatrace.com/t/service-flow-calculation-of-the-response-time-contribution-metric/46416>\
**Category:** Open Q&A\
**Tags:** dynatrace-managed, services-classic, service-flow\
**Created:** [July 2, 2024, 12:39pm UTC](https://community.dynatrace.com/t/service-flow-calculation-of-the-response-time-contribution-metric/46416 "2024-07-02T12:39:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![marina\_pollehn](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/marina_pollehn/32/39120_2.png) [@marina\_pollehn](https://community.dynatrace.com/u/marina_pollehn)\
**Post date:** [July 2, 2024, 12:39pm UTC](https://community.dynatrace.com/t/service-flow-calculation-of-the-response-time-contribution-metric/46416/1 "2024-07-02T12:39:14Z")

</div>

Let’s use the example of the Dynatrace documentation to phrase the question.

When I am viewing a service flow of the easytravel customer frontend service, I am interested in for how big of a share in the response time, the Journey service is responsible.

 ![marina_pollehn_2-1719923638561.png](https://global.discourse-cdn.com/dynatrace/original/2X/4/41f128b87b920ab4affecdd7e07c8e600d98ac96.png)

In the documentation, the following is mentioned:

- _1—Average response time service_

- _2—Call percentage_

- _3—Call per request_

- _4—Average response time overall_

While everything else is clear, I wonder what the average response time of service is referring to. Does this mean the performance of the ENTIRE JourneyService? Let’s say the JourneyService has 5 different requests overall, 3 of them are rather quick, 2 of them rather slow. Only the three quick ones are ever initiated by the easytravel customer frontend, the two slow ones are doing other things and are not relevant to my service flow shown above. They are not initiated by the easytravel customer frontend. Will the **average response time in the service flow above** be the average of all 5 requests weighted by the number of calls or will only the 3 requests initiated by the easytravel frontend be weighted and are then used as the average response time of the JourneyService, as only these are relevant to my service flow?

Because to be honest, the other requests of the JourneyService which are not initiated by the easytravel frontend will not be contributors to the duration of easytravel and will therefore not be response time contributors in my flow.

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [September 22, 2025, 12:14pm UTC](https://community.dynatrace.com/t/service-flow-calculation-of-the-response-time-contribution-metric/46416/2 "2025-09-22T12:14:31Z")

</div>

[@marina\_pollehn](https://community.dynatrace.com/user/2456)&nbsp;- From my understanding, starting from left to right, the metrics displayed are the sum of the entire sheet. Then as we move one column to the right, you will then see the metrics for each service and the associated metrics per the selected service/disbursement. Which then duplicates this analysis logic as we continue column by column to the right.&nbsp; I hope this helps!