# Alerting profile behavior

**URL:** <https://community.dynatrace.com/t/alerting-profile-behavior/22954>\
**Category:** Alerting\
**Tags:** problems-classic\
**Created:** [January 24, 2020, 6:20pm UTC](https://community.dynatrace.com/t/alerting-profile-behavior/22954 "2020-01-24T18:20:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![henk\_stobbe](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/henk_stobbe/32/30434_2.png) [@henk\_stobbe](https://community.dynatrace.com/u/henk_stobbe)\
**Post date:** [January 24, 2020, 6:20pm UTC](https://community.dynatrace.com/t/alerting-profile-behavior/22954/1 "2020-01-24T18:20:13Z")

</div>

Hello,

Looking at below:

Availability immediate

Error immediate

Slowdown after 30

Resource after 30

Custom imidiate

When I have someone interested only in resource alerts, is it possible that within the 30 minutes this resource problem will be promoted to Slowdown or Availability and the Resource altert is not triggered?

KR Henk

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [January 24, 2020, 7:28pm UTC](https://community.dynatrace.com/t/alerting-profile-behavior/22954/2 "2020-01-24T19:28:14Z")

</div>

In general problems sometimes are merging over time. But resource problems shouldn’t merge with different classes of them. At least I’ve never faced such situation.

Sebastian

---

<div class="post-metadata">

**Author:** ![justin\_hogue](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/justin_hogue/32/19679_2.png) [@justin\_hogue](https://community.dynatrace.com/u/justin_hogue)\
**Post date:** [January 24, 2020, 7:44pm UTC](https://community.dynatrace.com/t/alerting-profile-behavior/22954/3 "2020-01-24T19:44:51Z")

</div>

I agree, you should still receive all of the alerts unless the conditions for which that alert would be triggered are no longer being met within the specified time frame.

---

<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 24, 2020, 8:15pm UTC](https://community.dynatrace.com/t/alerting-profile-behavior/22954/4 "2020-01-24T20:15:09Z")

</div>

[@Henk S.](https://answers.dynatrace.com/users/4080/view.html) The classes of problems will not merge. A slowdown is a slow down and the root cause might be due to a resource. You could see a slowdown on transactions and an alert on resources as the hosting service has 95% memory saturation. But since slowdowns are set to immediate, you might get alerted right away of a slowdown but you will not be alerted of a resource issues until 30 mins later.

Please review the following articles:

> **[Event categories](https://docs.dynatrace.com/docs/dynatrace-intelligence/root-cause-analysis/event-analysis-and-correlation/event-categories)**
>
> Learn about different categories of events and supported event types, along with their severity levels, and the logic behind raising them.

> **[Root cause analysis](https://docs.dynatrace.com/docs/dynatrace-intelligence/root-cause-analysis)**
>
> How Dynatrace analyzes problems to determine their root cause.

Let me know if you need any other assistance

---

<div class="post-metadata">

**Author:** ![henk\_stobbe](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/henk_stobbe/32/30434_2.png) [@henk\_stobbe](https://community.dynatrace.com/u/henk_stobbe)\
**Post date:** [January 25, 2020, 2:54pm UTC](https://community.dynatrace.com/t/alerting-profile-behavior/22954/5 "2020-01-25T14:54:34Z")

</div>

To. both, thanks for your reply, combining your answers with below article made it all clear,

[https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/basic-concepts/problem-impact-level/](https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/basic-concepts/problem-impact-level/?_ga=2.128841675.657669084.1579949112-974773043.1579025898)

So putting it all together it means:

within a class, when a problem promotes, you simply get two problems

thanks Henk
