What username should be in that email? The one that had a problem? Or the recipient of that incident email?
And - do you really want to have an email sent out for every user that is frustrated? How many users do you have?
The value(user name) we capture from the session and tagged to the UEM.we want that value in the email.
We want the Email for frustrated user in the Visit and in this mail the tagged value(user name).
let me know it is possible.
I want an email alert if any of my user getting frustrating experience.And I want the name of user who is getting frustrated user experience.
I am getting count of Satisfied,Tolerating,Frustrated users in visits.I want an alert if the frustrated count is increased by single count.
Hi - there is an option to implement this - but - before I tell you how this works I would like to understand how many users you have on your system and what your frustrated visit rate is. It is important because the option I have available will only work if you do not have too many different usernames that are frustrated. If you have thousands or even millions of users that might be frustrated over the course of weeks, months or years you may overload our performance warehouse.
So - let me first understand your use case a bit better and then we can figure out if the option I have in mind will work or whether we have to bring this to the engineering team to think about implementing this as an out of the box use case/feature.
PFB the Use case that we want to perform:
Email generate for support team when user has Frustrated visit
In the Subject of Email we want the Application Name.
Email body contains the username that we tagged for particular visit.
I understand that - but - do you have 100 users on the system where one or two are frustrated by day - or do you have thousands of users with hundreds being frustrated. that makes a difference in the way you want to handle it. receiving hundreds of emails per day would then probably not make sense
So - what you can do is the following:
#1: Create a new Visit based Business Transaction
#2: Define a Filter Measure of type "Visits - User Experience" to filter for the frustrated users: see image
#3: Define a Split Measure that returns your username
#4: Define an Incident on the "Count" Result of this Business Transaction and set an upper severe threshold of 1
This will now trigger an Incident for every Visit that is frustrated and because of the Split Measure the incident will include the name of the user
BE AWARE though - that - for every UNIQUE frustrated user you will have this Business Transaction will create a measure in the performance warehouse. So - if you you "just" have 5 per day you will be kind of fine. But - if you have 100s per day and that over a longer period you will end up with a lot of measures in your PerfWarehouse that you actually never use for charting anyway. So - please be careful with this - but - tell us how it works for you
From Prathameshi Joshi,
I just want to confirm whether it is possible to get email alert for frustrated user in real time. I tried it by creating business transaction which filters the visit by frustrated user experience and splitted it by application and measure which is giving user name but it is giving alerts approximately after 30 min. of end of visit. So is there any other way to get real time alert for frustrated user.
There is no other way in the moment. The reason why you see the 30 mins delay is because this is the default timeout of a UEM Visit. In order for dynaTrace to know whether a Visit is complete it needs to make sure that there is no additonal data coming in. Thats why we have the Visit Timeout setting which is typically the same timeout as you have on your AppSErver for your User Sessions.
The question that I have to you know is: "What is a frustrated user for you?". If you want to have immediate notification than you may need to do this on failed User Actions instead of the overall calculated User Experience for a Visit. In this case you could either work with Error Rules that detect certain errors (HTTP 500, ...) and then raise an incident for these - or - create a User-Action based Business Transaction instead of the Visit-based BT that I proposed earlier in this posting
Hi @Andreas Grabner: In our case, we have a lot of users and most of our visits are satisfied visits as seen in the below screenshot (data of past 24 hours).
Though the visits are categorized as satisfied visits, some of them have a few frustrated user actions which take a very long time (~3 mins) and we are receiving complaints from the users regarding the slowness. I would like to get alerts in such cases with the frustrated username in my email. What can I do? Below is a screenshot of one such visit: