Actually you can go from user session to particular purepath. Oposite way for know isn't possible. You can see backtrace of purepath, you will see which application it was then after click on Application you will see which action it was. But from this point I don't think it's way to go directly to user action isntance. Or I've missed something 🙂
Thank you Sebastian. We have updated the same to customer.
Customer has explained the scenario as given below
I tried application flow with my id – it took 10 mins for transaction to
tried same application flow with his id – it took 8mins for the same transaction
can view both requests with purepaths and also response times 8 min and 10 min in
requirement here is to know which user session took how much time either 8 or
we know 10 mins is with my id and 8mins is with his id. This info need to be
shown in oneagent tool as well..
Please help on the above
Thank you for reply Sebastian.
Actually, requirement is to go to purepaths from user sessions. Below is the scenario:
1.Customer has logged into application and hit the home page i.e,
2. After authentication (which took only few seconds), to load Home page it took 5 minutes.
Customer wanted to see the pure path of the homepage showing response time as 5 minutes. which we are not able to track.
We have gone through the user sessions with the IP address.
We could see the home page with response time as 2 milliseconds. (we assume this 2 ms is user actions).
Please guide us how to see the purepath with actual home page load time (if possible from user session) if possible please attach sample screenshot of navigation
If you don't see purepath connected to particular user action on waterfall there maybe some problems with beacon path (in application settings). We've had such problems before. There was problem with geting requests from root of the page. Can you share with us screen of this particular action waterfall what do you see?
As I understand correctly. You are waiting in browser 5 minutes after authentications. You don't see such long purepaths on service level, and user action is quick. I think it can be related with redirection between components. The question is if you auth service is monitored by dynatrace and if you are tracking serviceflow of login request how it looks? It should prezent you response time breackdown between authentication and loading page.
It's possible that page load is quick and issue is somwhere else, but it has to by analyzed.
Hi Siva P.
It's more user action related question (and its duration) than user session in itself
- long session (i.e. +8 min) doesn't mean you have a problem.
Please remember Dynatrace has implemented an APDEX to score and differentiate between Poor, Tolerating, etc.
If I understand your question correctly, in this specific case, I'd recommend to dig the following options:
I. Mark your request as a key one. Create custom incident for individual service (i.e. use max response time as a trigger). And then from the the App dashboard (and related service incidents / slow instances of key requests you'd drill-back to affected user sessions). Just give it a try to check if it works for you...
II. Another option, IMO the most smart & flex, is streaming the user sessions out to Elasticsearch node, and finally perform individual queries the way you want.
III. Check USQL (https://www.dynatrace.com/support/help/monitor/user-sessions/how-can-i-create-custom-queries-based-on-user-session-data/), and check following querry:
SELECT userId, useraction.* FROM usersession WHERE duration .... AND name ....
Thank you Slawek for your response
Actually we are able to find out the purepaths with high response time
Customer only wants to find out, for instance
User :A" tried accessing easy travel application. It took 8 minutes to load. Again
User "B" tried accessing the same easy travel application. For user 'B" it took 10 minutes.
From pure paths, we can see two rows with 8 minutes response time and 10 minutes response time respectively.
But, how to find out for which user (A or B) it took 8 mts time and for which user it took 10 min time.
You have to start analysis from user session and find there slow user actions.
filter sessions by action duration. For such huge amount of time there should be only few. Than you will have answear which user sessions contains such actions.
If you know which action is slow (base on purepath) you can also add filter for particular user action:
This is not ideal way but the only way I know for this point. You can also do what Slavek suggested. When you will mark those long actions as Key actions, dynatrace will rise Problems correlated to such long response time and put this actions as affected. Then you will have filtered by dynatrace particular users affected problem and information about server side root cause or impact.
Unfortunately you will not go from purepath to user action right now, it was possible in Appmon, in Dynatrace at least not now. I hope it will be possible in the future.
Thank you. We have tried the way as suggested by you and Sebestian. We are able to see the pure paths with correct response time. However, we are not able to see the user name anywhere. Please confirm if I can confirm the customer that it is not feasible to find the user in the purepaths i.e., who has taken how much time for the session.