We have a webapp with pages that generate many many cascading XHRs.
We'd like to have an implementation that could give us the performance of those pages.
Even having used the "Extend action durations with cascading timed actions", the auto UA capturing did not help us. So we're considering a suitable custom-actions implementation.
I'd like to ask:
1) Can a custom action implementation (using: dtrum.enterAction(..) / dtrum.leaveAction(action)) live side by side with the auto-UA-mechanism?
-In appmon we actually had to turn it off because the 'currently active user action' was erratic and requests would be scattered inconsistently between the custom UA and the auto mechanism's UA.
2) Can the auto-UA-mechanism be disabled? How do I do that?
*without disabling the auto-injection itself.
3) What's the best way to group those XHRs together?
Currently considering using something of this sort:
actionId = dtrum.enterAction("my page load")
1) As far as I know, if you are adding custom actions on events that the content capture setting will catch, then you need to switch off the the automatic action detection.
2) You can use to enables or disables automatic action detection
3) You can check also if the use of enterXhrAction with xmode=2 will do the trick of adding subaction