# Is Dynatrace 'aware' if CPU/Memory high utilization is worth it or due to some issue?

**URL:** <https://community.dynatrace.com/t/is-dynatrace-aware-if-cpu-memory-high-utilization-is-worth-it-or-due-to-some-issue/31319>\
**Category:** Alerting\
**Tags:** problems-classic\
**Created:** [April 30, 2021, 11:05am UTC](https://community.dynatrace.com/t/is-dynatrace-aware-if-cpu-memory-high-utilization-is-worth-it-or-due-to-some-issue/31319 "2021-04-30T11:05:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [April 30, 2021, 7:06pm UTC](https://community.dynatrace.com/t/is-dynatrace-aware-if-cpu-memory-high-utilization-is-worth-it-or-due-to-some-issue/31319/2 "2021-04-30T19:06:25Z")

</div>

When Dynatrace alerts, it will include the root cause. If it’s like Garbage Collection, it will probably mean “bad”, but it might be to a long query as you say, and the root cause will identify the query, which might be “not that bad”. Not all problems will have a root cause, but I can guarantee you that should be the first thing to look for…

---

_[View the full topic](https://community.dynatrace.com/t/is-dynatrace-aware-if-cpu-memory-high-utilization-is-worth-it-or-due-to-some-issue/31319)._
