# Alerting on frustrating user sessions

**URL:** <https://community.dynatrace.com/t/alerting-on-frustrating-user-sessions/37912>\
**Category:** Real User Monitoring\
**Tags:** real-user-monitoring-classic, application-monitoring, usql, user-sessions\
**Created:** [January 8, 2023, 2:15pm UTC](https://community.dynatrace.com/t/alerting-on-frustrating-user-sessions/37912 "2023-01-08T14:15:58Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Peter\_Youssef](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/peter_youssef/32/14668_2.png) [@Peter\_Youssef](https://community.dynatrace.com/u/Peter_Youssef)\
**Post date:** [January 8, 2023, 2:15pm UTC](https://community.dynatrace.com/t/alerting-on-frustrating-user-sessions/37912/1 "2023-01-08T14:15:58Z")

</div>

Concerning alerting on Frustrating user sessions I’ve created a metric through USQL to be alerted on and the application owner being notified.

Is there another tested practical way to alert on Frustrating user sessions in Dynatrace.

Thanks.

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [January 9, 2023, 4:07pm UTC](https://community.dynatrace.com/t/alerting-on-frustrating-user-sessions/37912/2 "2023-01-09T16:07:17Z")

</div>

[@Peter\_Youssef](https://community.dynatrace.com/user/51369)&nbsp;at this point in time it does not exist in the product to be alerted on those values. 😞 I recommend tossing in a RFE for this if it is a core need for your organization.

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [January 9, 2023, 4:23pm UTC](https://community.dynatrace.com/t/alerting-on-frustrating-user-sessions/37912/3 "2023-01-09T16:23:08Z")

</div>

[@ChadTurner](https://community.dynatrace.com/user/14877)&nbsp;not true, this is possible using current functionality.  
[@Peter\_Youssef](https://community.dynatrace.com/user/51369)&nbsp;you can create [user session query metric](https://www.dynatrace.com/support/help/shortlink/rum-custom-metrics-user-sessions)&nbsp;for frustrated sessions and then use [Metric events](https://www.dynatrace.com/support/help/shortlink/metric-events)&nbsp;to alert on the metric.

For example:

 ![Julius_Loman_0-1673281186814.png](https://global.discourse-cdn.com/dynatrace/original/2X/f/fcef93113b7109478568757249a4cbccdd3af787.png)

add filtering conditions as desired. Or you can use the userExperienceScore as dimension and then you can have counts with satisfying/tolerating/fustrating user experience.

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [January 9, 2023, 4:35pm UTC](https://community.dynatrace.com/t/alerting-on-frustrating-user-sessions/37912/4 "2023-01-09T16:35:43Z")

</div>

I stand corrected, I was looking just at the custom metrics section. thanks&nbsp;[@Julius\_Loman](https://community.dynatrace.com/user/3364)

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [January 9, 2023, 8:33pm UTC](https://community.dynatrace.com/t/alerting-on-frustrating-user-sessions/37912/5 "2023-01-09T20:33:04Z")

</div>

I just noticed the only downside is it will cost DDUs - but if you have the funding why not lol

---

<div class="post-metadata">

**Author:** ![Peter\_Youssef](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/peter_youssef/32/14668_2.png) [@Peter\_Youssef](https://community.dynatrace.com/u/Peter_Youssef)\
**Post date:** [January 12, 2023, 6:54pm UTC](https://community.dynatrace.com/t/alerting-on-frustrating-user-sessions/37912/6 "2023-01-12T18:54:30Z")

</div>

Thanks [@Julius\_Loman](https://community.dynatrace.com/user/3364)

---

<div class="post-metadata">

**Author:** ![tyler\_rowe](https://avatars.discourse-cdn.com/v4/letter/t/4da419/32.png) [@tyler\_rowe](https://community.dynatrace.com/u/tyler_rowe)\
**Post date:** [January 16, 2023, 10:22pm UTC](https://community.dynatrace.com/t/alerting-on-frustrating-user-sessions/37912/7 "2023-01-16T22:22:12Z")

</div>

Great solution!

One thing to keep in mind when using User Experience Score is that it is a session level metric, so if there are multiple applications within the session, another application could be the primary driver for the frustrated experience. It is worth reviewing the User Experience Score settings to ensure they’re configured correctly for your use case (eg. turn off the “If last user action in a session is classified as frustrating, classify the entire session as frustrating” option if you do not wish for one action to mark an entire session as frustrated).
