Alert messages

An alert message contains a list of updated current values for alert types, when the alert message contains the current update value for alert types. Alert types include error count, inbound queue depth, file size, and others. Update values include idle CPU%, disk % full, disk free space, and others.

These values are the values that were available for the sources when the alert was fired. Some of the values might not be involved in causing the alert to fire.

For example, a queue depth alert that repeats every 60 seconds might have the first message be similar to:

Thread inbound queue depth of at least 2 of conn_1,conn_2,conn_3 has
		  been more than 15 for 30 seconds. Currently, conn_1 is 20,conn_2 is 25,conn_3
		  is 5.

The next updated message might be:

Thread inbound queue depth of at least 2 of conn_1,conn_2,conn_3 has
		  been more than 15 for 90 seconds. Currently, conn_1 is 22,conn_2 is 29,conn_3
		  is 12.

If an action needs to know the current repetition, then use the %R substitution characters.

Customized alert messages

You can append custom text to the alert message in the Message field.

You can also set up custom messages from within Cloverleaf so that they display on the GM server under the alert view. This includes % variables for alert values.

For example, when appending a message, there is {appended message} under ACTION:

{ALERT 
    { NAME Alert_1 }
    { VALUE status }
    { SOURCE bouncefile }
    { WITH -1 }
    { COMP {== down} }
    { FOR once }
    { WINDOW */*/*/* }
    { ACTION {
        { notify {} {appended message} }
        { message {xxx } }
    } }
}

When the message is fully customizable, there is no {appended message} under ACTION :

{ALERT 
    { NAME Alert_1 }
    { VALUE status }
    { SOURCE bouncefile }
    { WITH -1 }
    { COMP {== down} }
    { FOR once }
    { WINDOW */*/*/* }
    { ACTION {
        { notify {} }
        { message {message content} }
    } }
}