I'm having trouble with purepaths showing only the front-end actions on a JAVA instance. Both ".ear" are in the same JBOSS server and when the request reach any action who uses the backend it shows only the "wait" method while the backend do the actions requested.
Is there any way to show the methods of the "back-end" being called by the "front-end" action?
Just a couple thoughts here to help get down to whats going on here.
Is the backend java process instrumented with a dynatrace app mon agent? If so are the necessary sensors placed (usually selecting java technology in the agent group would be enough to get started). If both of the above questions are true if you select the show all nodes option for the given purepath (found in the purepath tree top right side) does that show the methods your interested in? Hope this helps.
Hi Nathan, sorry for the bad english
The backend and the frontend java process are running on the same AppServer instance (JBOSS/TOMCAT).
In the same dashboard you saw above "show all nodes" does not show anything of the backend, it only shows something if I place a sensor manually at the class and only works if I put it to start a purepath from the class.
maybe I'm missing something to improve the autosensor...
If you want a method to always show in the PurePath, a method sensor is required, Auto sensors will usually pick up bottlenecks, but depending on the sample rate, a fast running method may not be picked up often. Remember, AppMon is not a profiling tool, so it does not show every method invocation, only the ones that have sensors and whatever the auto sensors can detect. If you are consistently missing auto sensor methods, it may be due to not much overhead being available for auto sensors.
Also, you mentioned it "only works if I put it to start a purepath from the class". Are you seeing one PurePath and the method appears on an existing PurePath? If so, the start PurePath option is not coming into play. If you are seeing two PurePaths, then the reason the first PurePath doesn't show the method you expect, is that is happens on another thread that is not currently being traced as you are expecting.