Alerting profile in new tennant

[Jesahel08]

Hello everyone, I'm working with Dynatrace on a new tenant, but they no longer have Alerting Profiles or Problem Notifications enabled. We are currently handling problem notifications through Workflows, but I can’t manage notification delays based on error types to avoid receiving too many emails in my inbox.

With Alerting Profiles, it was possible to configure a waiting time before a problem triggered an email notification. Does anyone know how Alerting Profiles can now be managed or replaced in the new setup?

[Julius_Loman]

@Jesahel08 alerting profiles + problem notifications have been replaced with Workflows. You can create delayed notifications using full workflow functionality (which has some cost implications). However, this should be solved shortly. See more here .

[Jesahel08]

Hello,

The issue is that I’m unable to implement the delay by problem type through the workflow, since there are multiple problem category types. The problem trigger captures the issue instantly.

I tried adding additional logic before sending the email in order to create a time loop/delay before notifying the problem, but I wasn’t successful.

I’m not sure if you already have any implemented structure or approach that could help with this scenario.

Thank you.

[sujit_k_singh]

Hi @Jesahel08 

The trick is to not send immediately — instead, re-check if the problem is still active after a delay.

Pattern:

Problem Trigger fires → add a Run JavaScript action with conditional delay logic per category

Then add a DQL Query action that re-checks if the problem is still active after that delay

Condition → if still active → send email; if closed → do nothing

This thread covers the same approach Solved: Workflow trigger if the problem persists for at least 5 minutes - Dynatrace Community

Thanks,

Sujit

[sonja]

Hi @Jesahel08, we are adding this functionality into the problem trigger of workflows: in the next couple of months, you'll be able to select a predefined duration (5 mins, 10 mins, 15 mins, 30 mins, 60 mins, 2 hours, 4 hours, 24 hours and 7 days) from a dropdown in the problem trigger. The workflow will only be triggered once the problem has been opened for the selected duration.

Happy to update this post once this feature has been rolled out. 

In addition to using this functionality, one recommendation that we are passing to users is also evaluate why those problems are created, if the alerting conditions make sense and if it's possible to improve them to reduce the amount of alerting noice.

Sonja