As of xMatters version 5.0, this method has been deprecated, and should not be used. Instead, use setDeviceThreshold to set the notification's priority level for Device filtering, and the xm_priority @event token to set the Event's priority level. For any existing implementations, this method will no longer affect Device Engine handling.
Sets the priority of the notification. This priority will be used for both the filtering of Devices and determining how the notifications are sent to Device Engines. Specifically, xMatters sends out new live notifications in order of priority, so HIGH priority notifications are sent to a Device Engine before MEDIUM or LOW priority notifications.
The default event priority value for a notification is MEDIUM.
Users can set a minimum priority level of notifications for each of their Devices using the Priority Threshold setting in the xMatters web user interface. When resolving the notification, only notifications that meet or exceed the priority threshold are delivered to the Device.
@notification::setEventPriority(String priority)
(String) priority: the priority to assign to this notification; possible values are HIGH, MEDIUM, and LOW, or the corresponding short forms of H, M, and L. If the value does not match one of the possible values or its corresponding short form , the notification is set to the default priority of MEDIUM.
None
This script illustrates using setEventPriority to set a HIGH priority so that all Devices will be notified:
# Set Event Priority to HIGH to notify all Devices
@alert::setEventPriority("HIGH")