Skip to Content
Information
Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Example 1: Escalating an ALERT from lowest to highest priority

The ALERT in this example will be upgraded from Informational to Critical priority over five intervals.

The following list describes the properties of the ALERT:

  • The original priority of the ALERT is Informational ( PRIORITY(info) ).
  • The ALERT’s priority will be upgraded ( Escalate(up) ).
  • The priority will be upgraded gradually over the intervals of 10 minutes, 20 minutes, 30 minutes, 30 minutes, and 40 minutes ( Interval(10,20,30,30,40) ).

  • When the ALERT reaches the final priority level, the ALERT should be deleted

    ( Dispose(delete) ).

REXX EXEC example:

"AOEXEC ALERT KET(KEY1) TEXT('test alert') PRIORITY(INFO) ESCALATE(UP)" ,
  "INTERVAL(10,20,30,30,40) DISPOSE(DELETE) SSID(RE61)"
            1  2  3  4  5

CLIST example:

AOEXEC ALERT KET(KEY1) TEXT('test alert') PRIORITY(INFO) ESCALATE(UP) +
     INTERVAL(10,20,30,30,40) DISPOSE(DELETE) SSID(RE61)
              1  2  3  4  5

When the EXEC that is associated with this ALERT is scheduled, the ALERT’s original priority is Informational. After 10 minutes (1), the priority is upgraded automatically from Informational to Warning. The ALERT stays at the Warning priority for 20 minutes (2) and is upgraded to Minor. The ALERT stays at Minor priority for 30 minutes (3) before being upgraded to Major. It stays at Major priority for 30 minutes (4) before being upgraded to Critical. After remaining at Critical for 40 minutes (5), the ALERT is deleted.

Related topic

General-examples-of-AOEXEC-ALERT

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation 8.3