Finding who is executing a query

The PurePath should show you where this statement gets called from. You may not see the direct calling method as you probably dont have a sensor for it. If the transaction runs slow you will see Auto Sensor Data which can give you more details on where the call comes from.

A best practice is to define some custom sensor rules for your data access layer API. That will give you more visiblity.

If you want - export one of these PurePaths and send it over as part of my http://bit.ly/sharepurepath program. Happy to give you some feedback on the PurePath

Hi Andi,

in my case I don't see it.

I check if I'm allowed to send a purepath.

Pierre

hi andi,

I've defined a sensor on a specific method, and added jdbc sensor.

if while dynatrace is recording the purepath, there is a listener on an event occuring in the purepath, what happens with the listener ?

I suspect a listener which triggers the delete, and this delete is recorded in the purepath, but i don't have the listener trapped.

what do you think about this ?

Hi Andy,

here some news.

In fact, it seems to be due to an hibernate bug. We've replace a set by a list in an delete deappears.

Furthermore we are handle fetch manually.

Causing some curious things in dyntrace.

Regards.

Pierre

Hi Piere

Any more details on that hibernate bug? Would be cool if you could share your PurePath. I wont share any confidential information

As to your questions from March 4th. If you have listeners then dynatrace should be able to show you these listener executions. We support most of the common thread pools. if these listeners are executed in the main thread or in async threads we should show them as part of your inital PurePath that triggered these inserts, updates, ... if you dont see them I suggest you specify custom sensors for your listeners and configure them with "active and start purepath". Then you will definitely get PurePaths for these listener invokations

Andi