• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Richard M. · Jun 25, 2014 at 07:30 PM ·

Web Request Response Time

Hi,

 

We have encountered a situation like the below on some transactions that make it look like 5 seconds was spent doing a web request from an apache web server to an application backend server but according to the "Elapsed time" this only goes up until 5ms and the "Exec Total" time is also not adding up to this. This kind of gives a false positive in that it looks like the Apache web server is the cause for the slow response of the transaction. Are we interpreting this incorrectly?

 

If anyone wants I can send them the actual exported purepath to look at it.

 

From the transnational flow it also looks like 86% of the time was spent on the web server tier?

I have attached the call stack tree.Call Stack Tree.xlsx

 

Kind Regards

Richard

 

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

1 Reply

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Andreas G. · Jun 25, 2014 at 10:54 PM

Hi Richard

Any chance you can also export the PurePath? Makes it a little easier to read - or - maybe attach a screenshot of the PurePath so you can blank out information you dont want us to see.

If I look at the Excel file it seems that most of the time is "spent" when handing the request from Apache to Java. The Elapsed time indicates that the JVM doesnt get to handle that reqeust until 4,08s. Typically this can be explained if the JVM cannot accept the incoming requests fast enough, e.g: running out of worker threads. Therfore the request is put in a queue and picked up at a later time. that woudl explain it

I would look at the Threads in Java -> you can see that in the Process Health Dashboard.

Another thought: are these two servers running on the same or different physical machine? If they run on a different machine you may also have some delaying factors between these two containers, e.g: network constraints or a components such as a firewall/proxy between these two tiers.

Andi

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Richard M. · Jun 25, 2014 at 11:35 PM 0
Share

Thanks for the response Andreas if this is the case it makes perfect sense but the elapsed time is displaying milliseconds though not seconds thats why its just a bit confusing to me?

I will e-mail you the purepath

Kind Regards

Richard

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

No one has followed this question yet.

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A