# Response time distribution on Apache **URL:** \ **Category:** Dynatrace API\ **Tags:** distributed-traces-classic, apache, dynatrace-api\ **Created:** [January 21, 2020, 2:03pm UTC](https://community.dynatrace.com/t/response-time-distribution-on-apache/22937 "2020-01-21T14:03:54Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![shashank\_b\_agra](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@shashank\_b\_agra](https://community.dynatrace.com/u/shashank_b_agra)\ **Post date:** [January 21, 2020, 2:03pm UTC](https://community.dynatrace.com/t/response-time-distribution-on-apache/22937/1 "2020-01-21T14:03:54Z")
![23343-api-slow-response.jpg](https://global.discourse-cdn.com/dynatrace/original/2X/f/f4c2a4fbad6ab333353db595907807422cf31c34.jpeg) Hi I have recently installed Dynatrace on one of my Apache node. One of my API is responding very slow causing the bad user experience and I am trying to get to the bottom of it. While analyzing when i select purepath, I see something like screenshot attached. In the section top findings it says the 7.8 seconds it is taking belongs to Apache Module and there is one more option. When i click on apache Module it says 92.6% contribution from mod\_proxy and nothing is available after that. What does this mean? Does it indicates there is something wrong with my mod\_proxy of Apache? If yes what is it? How do i find out? Please guide me to dig a bit deeper to find out the cause. Appreciate any help ---
**Author:** ![rastislav\_danis](https://avatars.discourse-cdn.com/v4/letter/r/b9bd4f/32.png) [@rastislav\_danis](https://community.dynatrace.com/u/rastislav_danis)\ **Post date:** [January 21, 2020, 3:00pm UTC](https://community.dynatrace.com/t/response-time-distribution-on-apache/22937/2 "2020-01-21T15:00:54Z")
have you checked name resolving on apache server ? ---
**Author:** ![shashank\_b\_agra](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@shashank\_b\_agra](https://community.dynatrace.com/u/shashank_b_agra)\ **Post date:** [January 21, 2020, 3:24pm UTC](https://community.dynatrace.com/t/response-time-distribution-on-apache/22937/3 "2020-01-21T15:24:42Z")
[@Rastislav D.](https://answers.dynatrace.com/users/15936/view.html) Thanks for your response. I am sorry but what needs to be checked? Can mod\_proxy be responsible for performance issues? If you can elaborate that would be very helpful ---
**Author:** ![rastislav\_danis](https://avatars.discourse-cdn.com/v4/letter/r/b9bd4f/32.png) [@rastislav\_danis](https://community.dynatrace.com/u/rastislav_danis)\ **Post date:** [January 21, 2020, 4:17pm UTC](https://community.dynatrace.com/t/response-time-distribution-on-apache/22937/4 "2020-01-21T16:17:04Z")
not sure what is your cause, but can check your apache config, look how your request is passed through and check if host names (if used) are resolvable. ---
**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\ **Post date:** [January 21, 2020, 7:40pm UTC](https://community.dynatrace.com/t/response-time-distribution-on-apache/22937/5 "2020-01-21T19:40:59Z")
You have the answer right on the top right in the top findings section. It’s not the apache as it is just proxying the communication but the proxied api (you have the right url there). The mod\_proxy hotspot is just a result of the api itself. For the diagnosis, you have to analyze the hotspot at the called service.