• 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 Chris S. · Oct 23, 2013 at 05:18 PM ·

Asynchronous Elapsed Time Question

Greetings All,

I am new to asynchronous calls within dT and am having issues correlating all of the elapsed times to the appropriate call outs. I am attaching a session file in which there is one PurePath that takes 185 seconds in duration. I have been able to correlate all of the external calls, however there is one huge gap between ~64 seconds and ~185 seconds that seems to go unaccounted for.

Background on the application

This is new application to dT monitoring and have no instrumented methods other than auto-sensors and there may exist a load balancer between JBOSS and DB tier.

Background on the session

This is a single transaction of a "validation" step made within the end user's web browser.

Please let me know if you have any other questions.

Thanks

Chris Sechler

TradePortal_Asynchronous.dts

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.

3 Replies

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

Answer by Chris S. · Oct 24, 2013 at 02:24 PM

Christian,

Thanks so much for the research and responses. Since 5.6 will be released soon, this is most likely the route I will take. However, I will consult with my client to see what route they wish to take. 

Chris

Comment

People who like this

0 Show 0 · 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

Answer by Christian S. · Oct 24, 2013 at 02:12 PM

after some research i found out that there was a bug in dynaTrace 5.5 which affected auto-sensor matching in conjunction with JDBC statement aggregation. this was already fixed some time ago in a fixpack and will also be fixed in the upcoming dynaTrace 5.6 release. so in your case you would have multiple options:

  • turn off JDBC statement aggregation to get better auto-sensor data
  • wait for 5.6 to be released soon to have this bug fixed
  • try out the fixpack

hope this helps

Comment

People who like this

0 Show 0 · 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

Answer by Christian S. · Oct 23, 2013 at 06:44 PM

hi Chris,

i guess your question is: what happened between 64 and 185 seconds, right?

so basically this has nothing to do with asynchronous calls at all, because all of this happens on one thread (PMTPPoolID-1-UNBOUNDED-threadID-21 <1910437121>). so what we can say so far is that in these 121 seconds no database access happens, but not what actually really happens.

usually you should get more information by auto-sensors in this scenario, but i guess there's some auto-sensor matching issue on this PurePath. because in the 185s there were 12314 auto-sensor samples captured which would result in one every 15ms. however, this PurePath has a very recurring structure with all the getConnection()s which makes auto-sensor matching really difficult. in 5.6 where we will have connection aggregation as well, the structure of this PurePath will be somewhat simpler.

right now I can talk to R&D and see if we get some more information about your PurePath and keep you posted.

best,

Christian

Comment

People who like this

0 Show 0 · 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.

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

1 Person is following this question.

avatar image

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