19 Nov 2021 05:58 AM - last edited on 19 Nov 2021 06:24 AM by AntonioSousa
Hello, I'm monitoring the environment and I've noticed that several requests are getting a high response time in "Client-Side Response Time" or light blue bar in PurePath view. The API runs on Windows servers and IIS. I would like some help in identifying the possible causes so that only a few requests have this high processing time. Apparently, processing occurs but the API takes a long time to respond to the client, generating a timeout in every transaction.
Solved! Go to Solution.
This can happen for several reasons I quickly remember:
Most likely as @AntonioSousa writes the shortage on socket/thread/pool - whatever is used to establish the communication. Other reasons mentioned would have an effect on most of the requests.
I'd also suggest checking the Code-level tab in your PurePath (at the calling service node), maybe you can find some additional information there.
I compared two requests (one successfully and the other with the client-side with high response time) and identified that both perform exactly the same activities. In other words, the system processes the request but for some reason there is an excessive delay in the response to the client. In this case, could it still be something related to threads and pool? Unfortunately, at code-level there is no information regarding the light blue purepath bar.
Yes, all possibilities still apply. Your problems are certainly occurring before your code starts executing. You can eventually get more information by looking at the following points:
To understand the problem better, let us know if these requests happen always in the same host, or if they happen between distinct servers? If it's the latter case, as I suspect, please consider investigating what happen in between (load balancers, firewalls, etc.)
APIS are distributed across 6 identical servers and traffic is controlled by the load balancer. The problem occurs on some transactions but on all servers.
So, I believe there are 6 servers that are receiving the calls you mentioned above.
Can you tell us a little bit more on who is making the requests. If you have client side timings, it means that you have servers that are being monitored also by OneAgent, and are making the calls. Can you tell us a little bit more about them?
14 Dec 2021 03:31 PM - last edited on 15 Dec 2021 01:46 AM by AntonioSousa
Thanks again for your willingness to help. Calls are made from servers in the AWS cloud. I will attach images from today's request.
As a matter of caution, I have removed the attachment that you put here, not only because it is classified as confidential, but also because it really may contain sensitive information. I'm in the process of analyzing the information you provided, and will be back in a few minutes.
I have annotated the Purepath below. It does seem that times are quite high when invoking those services. They even continue working, despite the original client request being timed out at 1 minute.
For what I have seen you should concentrate your efforts on possibly two explanations for this:
in this case, my first move, is try to evaluate the argments. Your descrption seems finger point calls (front->Back). In 90% the issue come from code execution. Sometimes related to a "batch" who use ressources. If i cannot had access to code lvl, a comparaison with users session's waterfall may a good start point.( Compare ressource load by type of browser/Timesries/ressources/XRH or Load ?) etc etc