Visit End (Session ID) max of 60 minutes
We have a business transaction that identifies the 'user name' that logged into our application. The 'Visit Ends after user has been inactive" has been set to 30 minutes. Our session ID for the application is set to 90 minutes.
How can we continue to keep the 'user name' after the visit end time out by dynaTrace?
Hi Carlyle,
You can use the visit tagging mechanism to attach the "user name" to a visit. Just reuse the measure which you use for capturing and add it in the User Experience settings like on this screen.
Cheers Klaus
I would also suggest to set the UEM Timeout setting to the same 90 minutes that you have on your application server. With that - UEM will not identify multiple visits for the same user
We have already done that. The issue is not adding a "username". Setting it to 90 minutes is not allowed by dynaTrace.
So how can we continue to do this if dynaTrace does not allow it. Is there some other business transaction that will allow us to do this?
Hi,
Do you have a possibility to capture the username more than just once per visit? Maybe you send the name with each request and you can capture it again and tag the splitted visit. At the moment the limit is 60 min and can only be extend via a change in the system profile xml - which has the big downside that this setting will be overwritten the next time you change something in the UEM settings and you hit "Apply" or "Ok".
What you can do is add this as an RFE to the follwing forum Product Feedback and Enhancement Requests
Klaus
Hi Klaus,
I have come across a similar case in a Citrix environment where sessions can last several hours. The username is only visible when the user initially logs on and after that only a Session ID is visible in the PurePaths. This means that the first after 60 minutes of inactivity the first part of the session (visit) are is tagged with the username but after that a new visit is created that cannot be tagged by the username.
You described changing the Visit timeout limit manually in the system profile xml. Are there any other downsides to this besides it changing back when UEM settings are modified?
Ahmed
Hi Ahmed,
I think there is a bit of a misunderstanding. Changing manually means changing the default setting in the dt client to 60 min. This means that after a user was inactive/not creating any user action dt considers the visit as finished. The 60 min do not mean that you only get visits in the client that are 60 min long. They can last longer I have seen examples where a single visit lasted for days.
What is true is that during the running visit you have to capture the tag somewhere if that cannot be achieved the visit will not be tagged.
Cheers Klaus
Hi Klaus – I just edited part of my previous post for clarity. I was asking about changing the visit timeout manually (without the client) in the system profile xml file as you mentioned:
At the moment the limit is 60 min and can only be extend via a change in the system profile xml
Ahmed
Oh sorry my fault! Yes you can change that setting and the impact is that you should not edit the setting in the dt client anymore since it will not allow you to save the system profile with that setting. Also you should not go beyond that 60 min setting unless really necessary since it has an impact on the dt server holding the visits even longer in memory.
Thanks for clarifying that, Klaus! In that environment, I might have to resort to this manual edit of the system profile xml file if too many visits timeout over the lunch break.
