# Is anyone else having logic issues with "Frequent Issue" feature?

**URL:** <https://community.dynatrace.com/t/is-anyone-else-having-logic-issues-with-frequent-issue-feature/33954>\
**Category:** Alerting\
**Tags:** problem-detection, problems-classic\
**Created:** [January 31, 2022, 10:48pm UTC](https://community.dynatrace.com/t/is-anyone-else-having-logic-issues-with-frequent-issue-feature/33954 "2022-01-31T22:48:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ct\_27](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/ct_27/32/10499_2.png) [@ct\_27](https://community.dynatrace.com/u/ct_27)\
**Post date:** [January 31, 2022, 10:48pm UTC](https://community.dynatrace.com/t/is-anyone-else-having-logic-issues-with-frequent-issue-feature/33954/1 "2022-01-31T22:48:43Z")

</div>

We’re having logic issues with the “Frequent Issue” feature in that sometimes it doesn’t catch flapping and in other times is over suppresses events and we don’t get alerts on critical production issues.

If you haven’t already, read this&nbsp;[Detection of frequent issues — Dynatrace Docs](https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/problem-detection/detection-of-frequent-issues)&nbsp;to understand Dynatrace’s definition of it.&nbsp; I don’t feel as though the logic entirely handles the clients needs.

We also notice that this feature is an all-or-nothing feature.&nbsp; It’s only configurable at the global level and it has no sub-customizations other than on/off.&nbsp; Considering it’s sort of an AI feature, I figured there would be some way to also teach the AI, such as if it applies in areas it should not we could check a box that tells the AI that it behaved incorrectly, and thus the AI could learn.

Has anyone else had issues with “Frequent Issues” feature?

---

<div class="post-metadata">

**Author:** ![AntonioSousa](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antoniosousa/32/50_2.png) [@AntonioSousa](https://community.dynatrace.com/u/AntonioSousa)\
**Post date:** [February 1, 2022, 9:39am UTC](https://community.dynatrace.com/t/is-anyone-else-having-logic-issues-with-frequent-issue-feature/33954/2 "2022-02-01T09:39:10Z")

</div>

Yes, I’ve had problems in the past, and I investigated it deeply at the time. I even did the formula in the “Example” drop-down of the link above. It was working as announced. I can say though that it is particularly difficult to understand, mainly in edge cases, as was my case at the time.

I also second that some configurability should be available, because the only thing that can be done at the moment is disabling it altogether:

 ![AntonioSousa_0-1643708292392.png](https://global.discourse-cdn.com/dynatrace/original/3X/c/2/c2cb6b1d379e0961c1302a81522ab49ab9973164.png)

In the meantime, I joined several related Product Ideas referencing this in:  
[https://community.dynatrace.com/t5/Dynatrace-product-ideas/RFE-Ability-to-view-all-frequent-issues/idi-p/151029](https://community.dynatrace.com/post/151029)

---

<div class="post-metadata">

**Author:** ![dannemca](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dannemca/32/7215_2.png) [@dannemca](https://community.dynatrace.com/u/dannemca)\
**Post date:** [April 6, 2022, 2:49pm UTC](https://community.dynatrace.com/t/is-anyone-else-having-logic-issues-with-frequent-issue-feature/33954/3 "2022-04-06T14:49:46Z")

</div>

Sadly, the ability to have a granular option for frequent issues is not planned 😞

[https://community.dynatrace.com/t5/Dynatrace-product-ideas/Ability-to-enable-and-disable-Frequent-Issues-at-the-entity/idi-p/180105](https://community.dynatrace.com/post/180105)

---

<div class="post-metadata">

**Author:** ![ct\_27](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/ct_27/32/10499_2.png) [@ct\_27](https://community.dynatrace.com/u/ct_27)\
**Post date:** [April 6, 2022, 3:09pm UTC](https://community.dynatrace.com/t/is-anyone-else-having-logic-issues-with-frequent-issue-feature/33954/4 "2022-04-06T15:09:16Z")

</div>

thank you for connecting the dots. I posted additional comments in the linked post.
