# Preventing alerts on known problems

**URL:** <https://community.dynatrace.com/t/preventing-alerts-on-known-problems/20572>\
**Category:** Alerting\
**Tags:** problem-detection\
**Created:** [October 15, 2020, 8:13pm UTC](https://community.dynatrace.com/t/preventing-alerts-on-known-problems/20572 "2020-10-15T20:13:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [October 16, 2020, 7:43am UTC](https://community.dynatrace.com/t/preventing-alerts-on-known-problems/20572/2 "2020-10-16T07:43:57Z")

</div>

Usually, unless you have turned off the request issue detection in tenant settings, Davis would pick it up and won’t alert you unless the problem severity increases.

If this does not happen for you, then probably those problems differ. For example it is for a different user action. You might want to finetune your settings - in this example setting appropriate expected values for user action metric.

Also when considering user actions, and this is a common issue, you don’t have user action rules precisely defined. That means, different user activities result into the same user action name. Then you might experience high volatility values for the key user action metric and noisy alerting happens.

---

_[View the full topic](https://community.dynatrace.com/t/preventing-alerts-on-known-problems/20572)._
