Alert Profiling and Notification Complexity

[harsit1105]

Currently facing operational inefficiencies in managing alert profiling and problem notifications across multiple applications. Each application requires a separate and manually configured alert profile, leading to duplicated effort, inconsistent configurations, and increased risk of missed or delayed notifications. This fragmented approach hinders scalability, complicates maintenance, and reduces the overall effectiveness of the alerting system.

Is their any chance I can make use of workflow for dynamic per-app alert routing?

Note : Here I have created 2 auto-tags (1. App 2. OwnerEmail) which can be used during the token and mapping as per the app alert.

[Romanenkov_Al3x]

Based on practical experience, the optimal solution for customized requests is to create a simple application combined with a custom webhook integration. This allows embedding any required logic, limited only by the programming language. Furthermore, additional Dynatrace API calls can be implemented to fetch problems proactively, eliminating the need to wait for webhook triggers. The result is a robust tool with tailored logic for your customer or engineer.

Perhaps my approach isn’t the best (but it helped me learn golang), and maybe someone has a better method using standard settings.

Regards,

Aleksandr Romanenkov

[sonja]

Hi! yes, I would highly recommend to use workflow for that as that is the more flexible and future proof solution. 

Here is a very simple example on how to trigger an e-mail notification: https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/use-cases/workflows-tutorial-prob.... You need to make sure that all relevant fields tags you need have been propagated to the problem record. 

Here is a simple DQL query for a specific problem id:

fetch dt.davis.problems
| filter display_id == "P-2510175911"

Any of the data available on the problem record can be directly re-used into the workflow configured with a problem trigger. You can add tasks to fetch additional data if needed. And in the last task, you can configure who should receive the e-mail notification.