# Alert fatigue, Dashboards, recommendations?

**URL:** <https://community.dynatrace.com/t/alert-fatigue-dashboards-recommendations/54508>\
**Category:** Alerting\
**Tags:** problem-detection, problem-notification, anomaly-detection, problems\
**Created:** [December 30, 2025, 2:57pm UTC](https://community.dynatrace.com/t/alert-fatigue-dashboards-recommendations/54508 "2025-12-30T14:57:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kenny\_Gillette](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/kenny_gillette/32/20170_2.png) [@Kenny\_Gillette](https://community.dynatrace.com/u/Kenny_Gillette)\
**Post date:** [December 30, 2025, 2:57pm UTC](https://community.dynatrace.com/t/alert-fatigue-dashboards-recommendations/54508/1 "2025-12-30T14:57:22Z")

</div>

How are DT engineers working through Alert fatigue?

How are DT engineers figuring out best time for below (services, Web, etc)?

![Kenny_Gillette_0-1767106262783.png](https://global.discourse-cdn.com/dynatrace/original/2X/d/d277a4b5ac82ce90d0ed577e2b2aecddfbf7e1cc.png)

I know adjusting these settings is a balancing act between&nbsp; **speed** &nbsp;(MTTD - Mean Time to Detect) and&nbsp; **accuracy** &nbsp;(reducing false positives).

Anybody got any good dashboards or notebooks that help with this?

I got some various Problems dashboards that I can share if helpful but doesn’t look at how many problems at various times.&nbsp; Here is a dql we started to use to figure out some services.

fetch dt.davis.problems  
| filter event.status == “CLOSED”  
| filter affected\_entity\_types[0] == “dt.entity.service”  
| filter contains(event.name, “Failure rate increase”, caseSensitive:false) or contains(event.name, “Response time degradation”, caseSensitive:false)  
| fields timestamp, event.name, resolved\_problem\_duration, affected\_entity\_ids, root\_cause\_entity\_id  
| summarize count(), by: {resolved\_problem\_duration}

 ![Kenny_Gillette_2-1767106535373.png](https://global.discourse-cdn.com/dynatrace/original/2X/7/715600c24f1da1515f515f3f8e8316424dd13462.png)

---

<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:** [December 30, 2025, 9:58pm UTC](https://community.dynatrace.com/t/alert-fatigue-dashboards-recommendations/54508/2 "2025-12-30T21:58:40Z")

</div>

[@Kenny\_Gillette](https://community.dynatrace.com/user/36140)&nbsp;,

I have done this exercise with several clients. What seems to work best from my perspective:

1. Maintain 1 minute for “Failure rate” so MTTD is fast
2. In “Failure rate” start with a higher “Absolute threshold”. 1% and 5% have worked for me. More details below.
3. In “Response time”, an absolute threshold of 300 ms is my favorite. But it really depends on a lot of factors, and in Portugal, where the Cloud is not near, as latency is always a problem, that’s the reason I normally suggest it’s higher.
4. Pareto tells us that 80% of the problems will be on 20% of the Services. In my case, I normally see 95%/5%, so setting specific thresholds for specific Services yields great results… You can see them if you summarize by&nbsp;affected\_entity\_ids.
5. But in the end, the greatest way is to correct all those errors. Response time, is more difficult though…

Regarding #2 above, you can graph it with

```markup
fetch dt.davis.problems
| filter event.status == "CLOSED"
| filter affected_entity_types[0] == "dt.entity.service"
| filter contains(event.name, "Failure rate increase", caseSensitive:false)
| parse event.description, "DATA 'increased to ' ([0-9.]+):fail_raw ' %' DATA"
| fieldsAdd fail_rate = bin(toDouble(fail_raw),1)
| filter isNotNull(fail_rate)
| summarize count = count(), by: { fail_rate }
| sort fail_rate asc

```

and you might get something like

 ![AntonioSousa_0-1767131787112.png](https://global.discourse-cdn.com/dynatrace/original/3X/f/6/f6fc91cc0f2d77ea62d76515d319bf0072c525da.png)

In this case, more than a third of the problems were with error percentages below 6%.
