16 Apr 2026
12:04 AM
- last edited on
17 Apr 2026
07:16 AM
by
MaciejNeumann
Is there any way for customizing the alerting templates for Out of the box alerts generated by Dynatrace e.g. Azure App
Current notification email subject is
OPEN Problem P-xxxxxx: Azure App Service CPU percentage [Azure] on Azure App Service Plan azureplan-plan
Problem detected at: 22:41 (UTC) 1.04.2026
1 impacted infrastructure component
Azure App Service Plan
azure-plan-name
Azure App Service CPU percentage [Azure]
The CPU percentage value of 98 % was above your custom threshold of 95 %.
Root cause
Azure App Service Plan
azure-plan-name
Azure App Service CPU percentage [Azure]
The CPU percentage value of 98 % was above your custom threshold of 95 %.
16 Apr 2026 10:07 AM
Hi,
If you are talking about problem card generated by Davis AI, visible in Dynatrace console, that is not customizable.
But you can create your custom metric events classic, or anomaly detector, where you can set problem title, description...
Best regards
16 Apr 2026 11:29 AM
Hi,
Yes, to some extent, but not completely.
For problem notifications in Dynatrace, you can customize the email subject and body using your own template and placeholders such as {ProblemTitle}, {ProblemID}, {State}, {ImpactedEntityNames}, or {ProblemDetailsHTML}. This is configured in the email notification integration itself.
Here is the documentation with the available fields you can customize: Send Dynatrace notifications via email.
Send Dynatrace notifications via email
However, for out-of-the-box alerts generated by Dynatrace, such as Azure App Service alerts, you can’t change the native problem title or the original problem content generated by Dynatrace itself. What you can do is wrap that information in your own notification template and decide how much of it you want to show in the email. The underlying ProblemTitle still comes from Dynatrace.
If you need full control over formatting and notification logic, a better option is often to use Dynatrace Workflows with the Send email action, which gives you much more flexibility than the classic problem notification integration.
Email
Another workaround is what @AntonPineiro mentioned. I mean you can create custom metric events (classic) or anomaly detectors. In these cases, you can define your own problem title, description, and thresholds. This gives you full control over the alert content, unlike out-of-the-box alerts, but requires recreating the alerting logic manually.
Featured Posts