Dynatrace + Alert24 Integration: Problem Notifications to Incidents

Dynatrace's problem notification system can POST to a custom webhook URL when problems open or close. Pointing it at Alert24's incidents API gives you Dynatrace's AI-driven problem detection feeding directly into Alert24's incident tracking.

Before you start

You'll need:

• An Alert24 API key with write or incidents scope (Settings → API Keys)
• Dynatrace account with Settings access (Settings → Integration)

Create a custom integration

1. In Dynatrace, go to Settings → Integrations → Problem notifications
2. Click + Add notification
3. Set Notification type to Custom integration
4. Set Display name to Alert24
5. Set Webhook URL to https://app.alert24.net/api/v1/incidents
6. Under Custom headers, add:
   • Authorization: Bearer ak_live_YOUR_KEY
   • Content-Type: application/json
7. Set the Custom payload to:

   {
     "title": "{ProblemTitle}",
     "description": "{ProblemDetailsText}",
     "severity": "{SeverityLevel}",
     "alias": "dynatrace-{ProblemID}",
     "source": "dynatrace",
     "tags": ["dynatrace", "{ImpactedEntities}"]
   }
   

8. Under Alerting profile, select which problems trigger this notification
9. Click Send test notification to verify
10. Click Save

Severity mapping

Dynatrace uses its own severity levels. The {SeverityLevel} placeholder returns values like AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION. Since Alert24 expects critical/high/medium/low/info, you have two options:

Option 1 — Fixed severity: Replace {SeverityLevel} with a hardcoded value like "critical" for all Dynatrace problems.

Option 2 — Adapter: Route the webhook through a small Lambda or Cloudflare Worker that maps:

Deduplication

The {ProblemID} placeholder is Dynatrace's stable identifier for a problem instance. Alert24 deduplicates on the alias field — re-notifications for the same open problem increment the occurrence count.

Tips

• Alerting profiles: Dynatrace alerting profiles let you scope which problems trigger notifications (by severity, management zone, tag, etc.). Create a profile scoped to production entities to avoid incident noise from dev/staging.
• Auto-resolution: Dynatrace can send a separate notification when a problem closes. In that notification's payload, you can call PUT /api/v1/incidents with status: resolved using the same alias.
• {ProblemDetailsHTML}: Dynatrace also provides an HTML version of the problem details — use {ProblemDetailsText} (plain text) for the Alert24 description field for cleaner incident descriptions.