# Response time x response time measured by caller **URL:** \ **Category:** Open Q&A\ **Tags:** distributed-traces-classic\ **Created:** [April 3, 2023, 2:58pm UTC](https://community.dynatrace.com/t/response-time-x-response-time-measured-by-caller/39135 "2023-04-03T14:58:55Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![vitorsanders](https://avatars.discourse-cdn.com/v4/letter/v/a88e4f/32.png) [@vitorsanders](https://community.dynatrace.com/u/vitorsanders)\ **Post date:** [April 3, 2023, 2:58pm UTC](https://community.dynatrace.com/t/response-time-x-response-time-measured-by-caller/39135/1 "2023-04-03T14:58:55Z")
I wanna know the difference between the “Response time” and the “Response time measured by caller”. There is a service called by another service at the same cluster, the latency is small at this cluster but the difference is high when I choose the P95 view. Is it commun? Response time: ![vitorsanders_0-1680533774074.png](https://global.discourse-cdn.com/dynatrace/original/2X/b/b868f863245670a9fbc90a11eb3a45e28550e1a8.png) Reponse time measured by caller: ![vitorsanders_1-1680533813716.png](https://global.discourse-cdn.com/dynatrace/original/2X/2/2667a431cb77db48d85f7e7d96e1c6db0f536358.png) Thanks! ---
**Author:** ![radek\_jasinski](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radek_jasinski/32/10432_2.png) [@radek\_jasinski](https://community.dynatrace.com/u/radek_jasinski)\ **Post date:** [April 3, 2023, 4:22pm UTC](https://community.dynatrace.com/t/response-time-x-response-time-measured-by-caller/39135/2 "2023-04-03T16:22:28Z")
Hi, This is a two type of metrics (Service metrics and Client-side metrics): _Client-side metrics are measured from the time a request leaves your application to the time the response is received by your application._ _Server-side metrics are metrics as the name suggests directly on the server layer_ **Examples of metrics :** Service metrics: - Response time - Request count - Successful request count - Failed request count - Error count - Failure rate - HTTP 4xx count - HTTP 5xx count - CPU time - IO time - Wait time - Lock time - Number of calls to databases - Time spent in database calls - Number of calls to other services - Time spent in calls to other services Client-side metrics - Response time measured by caller - Successful request count as seen by caller - Failed request count as seen by caller - Failure rate client - Number request attributes Below you have an explanation of how this thesis looks at application testing. _Client-side a/b testing is best used when you are deploying an internal team of marketers to run experiments without the need for them to touch coding. Server-side a/b testing is best used when the scope of an experiment is bigger, for example, changes need to be made at the product level._ Radek ---
**Author:** ![Jan\_Lerche](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@Jan\_Lerche](https://community.dynatrace.com/u/Jan_Lerche)\ **Post date:** [April 13, 2023, 7:52am UTC](https://community.dynatrace.com/t/response-time-x-response-time-measured-by-caller/39135/3 "2023-04-13T07:52:19Z")
Hello Radek this is a very intersting topic for me. I have two additional questions here. Is there any documentation where you have found this list of metrics seperated by server and client? Second: Which prerequisite has to be fulfilled to get the ‘response time measured by caller’ out of the Dynatrace API? I can’t find this metric there. I think that this is not the same as the built in metrics for client-side response time and should not be mistaken. I hope you can help me to get further details. Thanks and best regards Jan ---
**Author:** ![radek\_jasinski](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radek_jasinski/32/10432_2.png) [@radek\_jasinski](https://community.dynatrace.com/u/radek_jasinski)\ **Post date:** [April 13, 2023, 8:29am UTC](https://community.dynatrace.com/t/response-time-x-response-time-measured-by-caller/39135/4 "2023-04-13T08:29:30Z")
Hi Jan, Hi, You can find the types of metrics that are available in Dynatrace here: [Built-in classic metrics — Dynatrace Docs](https://www.dynatrace.com/support/help/shortlink/built-in-metrics#response-time) - I’ve highlighted the section for Response Time for you right away. In general, these metrics are commonly used in application monitoring tools. You can find a lot of information not only in our documentation, but also on the Internet. Here you have a cool example for client-side: [Client-side metrics overview  |  Bigtable  |  Google Cloud Documentation](https://cloud.google.com/bigtable/docs/client-side-metrics) or [https://www.indeed.com/career-advice/career-development/server-performance-metrics](https://www.indeed.com/career-advice/career-development/server-performance-metrics) Response time measured by caller is builtin:service.response.client. Regards, Radek ---
**Author:** ![Jan\_Lerche](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@Jan\_Lerche](https://community.dynatrace.com/u/Jan_Lerche)\ **Post date:** [April 14, 2023, 11:38am UTC](https://community.dynatrace.com/t/response-time-x-response-time-measured-by-caller/39135/5 "2023-04-14T11:38:04Z")
Hello Radek thank you very much for your explanation. Where do you have the information from? The Dynatrace documention doesn’t tell anything about the intention of the metrics (following your [link](https://www.dynatrace.com/support/help/shortlink/built-in-metrics?_ga=2.39840928.2082122721.1681191547-716953091.1674459791#response-time) above that was already familiar to me). These metric descriptons would be essential for us. Same for the connection of Response time measured by caller and builtin:service.response.client. Where is this relationship documented? ---
**Author:** ![Kor01](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/kor01/32/19401_2.png) [@Kor01](https://community.dynatrace.com/u/Kor01)\ **Post date:** [April 14, 2023, 11:42am UTC](https://community.dynatrace.com/t/response-time-x-response-time-measured-by-caller/39135/6 "2023-04-14T11:42:49Z")
Having these metrics described better in the documentation would be incredibly useful. I just went down this same rabbit hole a few months ago and it was not easy to find the answers that should just be in the documentation