topic Re: Alerting profile behavior in Alerting

Alerting profile behavior

henk_stobbe — Tue, 18 May 2021 07:36:13 GMT

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

Re: Alerting profile behavior

skrystosik — Fri, 24 Jan 2020 19:28:14 GMT

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

Re: Alerting profile behavior

justin_hogue — Fri, 24 Jan 2020 19:44:51 GMT

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.

Re: Alerting profile behavior

ChadTurner — Fri, 24 Jan 2020 20:15:09 GMT

@Henk S. 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:

https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/basic-concepts/event-types/?_ga=2.111288455.2023751569.1579873345-1052794368.1579873345

https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/basic-concepts/how-problems-are-detected-and-analyzed/

Let me know if you need any other assistance

Re: Alerting profile behavior

henk_stobbe — Sat, 25 Jan 2020 14:54:34 GMT

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/

So putting it all together it means:

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

thanks Henk