Priority Field

Priority field of an integration defines the level of importance of an alert which is created by that integration. An alert may have one of the five different types of priority levels; P1, P2, P3, P4 or P5 (importance level decreases from P1 to P5).

The figure below shows the options that the customer can set as the priority of integration. You can select any of the P1, P2, P3, P4 or P5 manually or you can either select {{priority}} dynamic field or the Custom Value to Opsgenie Priority to define how you want to parse the priority from the payload.

If you select manual values, the alert created from that integration will always have that priority.

If {{priority}} dynamic field is selected, then it may have two different outcomes. If the integration sends a priority value and Opsgenie parses and maps it to its known priority levels, then the priority is set according to the priority value from the payload that the tool sends. If an unknown value is assigned or the tool does not carry a priority information, the alert will have the default priority value, P3.

If Custom Value to Opsgenie Priority is chosen a new field will be shown to give the expression to define how you want to parse the priority from the payload. The result must be one of the priority values that Opsgenie allows; P1, P2, P3, P4 or P5. You can drag dynamic fields and use string processing methods just like other field configurations. If the result is an unknown value, then the default priority value P3 is set as the priority of the alert.

Updated about a year ago


Priority Field


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.