Idea ID 2776437
The IDEA in this E/R is regarding RUM transactions over closed session.
There is no way to match transactions over closed session
Customer is using the following reports
- Applications -> Analysis Reports -> RUM Session Analyzer – To check the actions inside the sessions
- Applications -> Analysis Reports -> RUM Transactions Summary – To check quantity of the transactions
- Applications -> Analysis Reports -> Performance Raw Data – To check details of the detected transactions
- Admin -> End User Management -> Monitoring – To show you the actions that were used in each transaction
When the two actions sequential occurring actions are identified in different RUM sessions the transaction is not correctly recorded. The different sessions are automatically generated by RUM when the present session reaches 500 actions.
RUM should construct correctly transactions when one session of 500 actions ends and it creates automatically another session.
More details on this is once the second action was defined as optional the problem is that the reported time is this cases is a lot smaller that the correct time that it should be reported.
E/R is opened since, RnD team confirmed this can not be implemented as a hotfix in current version, but possible in newer versions.
Thank you for your time!
Real User Monitoring(RUM)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.