Using workflows for problem notifications, alert profiles, and management zone

[phongsakorn]

Currently, we are trying to migrate from flow management zones, alert profiles, and problem integrations to use simple workflows for alerting. However, we found that segments cannot be used in workflows for filtering, and there is no delay feature like in alert profiles. Both features are still listed as product ideas.

https://community.dynatrace.com/t5/Product-ideas/Delay-on-the-Davis-Problem-trigger-in-workflow/idi-...

Could you please provide an estimated release timeline for these features?

[rpindel]

Thanks for writing this up.  I was coming to the Community to write up more-or-less the same.  As we think about moving from Alerting Profiles/Management Zones/Integrations for alerting two things jumped out to us based on how the platform is currently implemented:

1. There is no way to invoke a Segment in a Workflow.  While we understand the technical details behind why this is the case, it is a drastic change from the ease of Management Zones and also feels lacking with regards to Workflows that do not serve alerting purposes.  We are still hopeful for work from the Workflow product team on bringing in Segments.
2. Alerting Profiles/Integrations allow us to alert on conditions and aside from any configured limits on the quantity, do not cost us anything extra.  We understand that simple Workflows are no-cost but a simple Workflow consists of two actions - a trigger and something else like a Slack message - but some alerting flows would need at least three if not more actions, especially considering the lack of Segments to effectively isolate the correct Problem events.  Workflows that have three or more actions are not considered simple and are charged.  We are concerned this essentially changes alerting for no-cost to alerting for cost.

I am adding my comments here ahead of routing this RFE to our CSM.

[sujit_k_singh]

Hello @phongsakorn 

I share the same concerns. To add to this thread:

On the delay feature: Until Dynatrace natively adds a delay to the Problem trigger, the workaround is to use a DQL re-check pattern — trigger fires instantly, then a subsequent action queries if the problem is still active after X minutes before notifying. It works, but it adds actions (and cost).

On the cost concern: This is the real issue. What was previously free (alerting profile + integration) now potentially costs DDUs once you exceed 2 actions in a workflow. Especially when you need extra actions just to work around missing features (delay, segment filtering).