• 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 Glenn M. · Feb 11, 2015 at 06:45 AM ·

CPU on Method Hotspots dashlet does not agree with Methods dashlet

We've found a situation where the underlying purepaths for a single Method Hotspots dashlet were inconsistent, depending on which method was selected.  Here are the details:

I selected 20 purepaths from the Purepath dashlet, and drilled down into Method Hotspots.  As the attached figure 1 shows, the top CPU user was info(Object, Object[]).  Further down on the list was process(Object, Writer).  If I go back to that same Purepath dashlet and those same 20 purepaths, drill down into methods, and sort by CPU Sum, I see something different (see figure 2).  Now process(Object, Writer) is the top CPU user.

Investigating further, I went back to Method Hotspots, selected info(Object, Object[]), and drilled down into Purepaths.  As expected, 20 purepaths were displayed.  Then I went back to Method Hotspots, selected process(Object, Writer), and drilled down into Purepaths...and only 1 purepath was displayed!

In other words, for the method-level data shown in the same Method Hotspots dashlet, info(Object, Object[]) represented an aggregation of 20 purepaths as expected, but process(Object, Writer) only represented a single purepath.  This gives a completely misleading picture of what the hotspots actually are of course.  Is there an explanation for this behavior?

BTW, this is a stored session, and the dashlet filters are set the same for all the dashlets involved.  We're using dynaTrace 6.1.

 

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.

4 Replies

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

Answer by Christian S. · Feb 19, 2015 at 12:50 AM

hi Glenn,

so far Andi's explanations were correct, the method hotspots dashlet takes auto-sensors into account whereas the method dashlet does not.
so this explains the CPU timing differences you see.

the drilldown from the method should result in all PurePaths where this method was actually called, so if it's really called in all 20 PurePaths then it is indeed interesting why it would only result in 1 PurePath.

as Andi asked: could you maybe export those PurePaths to a session and share that with us?

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.

avatar image

Answer by Andreas G. · Feb 13, 2015 at 12:44 PM

Thats correct. If that is the case it almost sounds like a bug in correctly applying the filter to the dashlet you drill down to. any chance you can share that exported session?

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 Glenn M. · Feb 13, 2015 at 12:20 PM

That makes a certain amount of sense, Andi, but even with that, it seems odd that drilling down into Purepaths from the process() method on MethodHotspots would only bring up 1 purepath.  It definitely was called in all 20 purepaths, and was instrumented.  Even if it wasn't instrumented, I can't imagine the sampling process used to populate MethodHotspots would have missed process() 19 out of 20 times.  I'll be interested to hear what the engineers have to say about it.

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 Andreas G. · Feb 13, 2015 at 11:17 AM

Hi. I think I have an explanation for this but I first want to check this with engineering if this is really the case. Here is my guess

The Methods Dashlet only shows "Instrumented" methods and therefore the CPU Data that we book on these PurePath Nodes that come in through our Sensors. The Method Hotspots Dashlet also includes Auto Sensors - which is more granular and has more methods. Now - if you instrument process and just look at that method (e.g: hide Auto Sensors in the PurePath tree) then you will probably see CPU Sum 1140. When you turn on Auto Sensors you will most likely see that this method also called other methods that got picked up by Auto Sensors. So the 1140ms is actually spread across several methods.

My assumption now is that the Methods Dashlet shows the Total CPU time that was booked on that instrumented node whereas the Method Hotspot just shows the time that was consumed in that method and shows all other "child methods" as additional hotspots with their share of the CPU.

Now - let me double check this with engineering as I am not sure if this is really correct. But it was my first thought when I looked at your screenshots

Andi

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

2 People are following this question.

avatar image 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