User Problem

Currently, Opsgenie's Dynatrace Webhook v2 integration (DynatraceV2) accepts and processes ProblemSeverity from Dynatrace as {{problem_severity}} and is displayed an an Extra Property (Severity) of an alert.

The apparent disconnect is that per Dynatrace's Opsgenie Integration doc, "Dynatrace availability problems are mapped to Opsgenie P1 incidents, error problems are mapped to P2, slowdowns are mapped to P3, and so on." 

Suggested Solutions

Would like to see Opsgenie's alert priority value mapped to the ProblemSeverity value as explained in Dynatrace's Opsgenie integration doc.

Current Workarounds

There are 2 similar workarounds:
1. Using Alert Policy to set the alert priority value according to the value of the Extra Property key "Severity" (whose value is based on the variable {{problem_severity}}).
2. Using Create Alert actions - The other workaround (explained in this community post) uses a Create Alert action to set each priority value depending on the value of the "Problem Severity" in the filter condition.