How to break one big PP into few small PP
Hi
We have some trouble with braking down one big Pure Path that start with "processImpl" into few Pure Path every time we find "process".
We define new sensor group called "ForceStartPP" with the 2 methods
and mark them with "Active and start new PP" in the sensor configuration part of the agent group
But we didn’t get the result we asked for (another small Pure Paths for every call of "process".
We tried to put the method "process" in different sensor group with higher priority , and also to switch the "active" to "active and start a new Pure Path" in the Sensor group and few other combination and didn’t had any successes.
The only way we got Pure Paths for the process method was when we made the "processImpl" inactive.
We also noticed that each Asynchronous invocation is started on a different thread..
Any help is appreciated J
Our version is "6.0.0.7153"
Attach is a stored session.
Tzaci & Yos
The behavior you're experiencing is by design, if there is already an active PurePath then it will not generate new ones downstream. You have two options:
- Set the sensor which defines "ProcessImpl" inactive (you've done that and know what the trade-offs are)
- Set the Thread Tagging sensor inactive. This will not only disable thread tagging for this type of transaction but all transactions which trace on this Agent Group. If you look at your other PurePaths and find that you don't need to trace across threads then it is safe to disable this sensor. With your created "active and Start PurePaths" rule you will get a separate PurePath for the parent processImpl and all its children process() calls
Does that help?
Rick B
Community Member of the Month
September 2018
Announcing Dynatrace's Community Member of the Month for September 2018, Muthu P.! Click here to read more! Employee Member of the Month
September 2018
Announcing Dynatrace's Employee Member of the Month for September 2018, Kris Z.! Click here to read more! 