A condition

Edit online

A condition specifies the event that should trigger a response. It does this using an event expression and, optionally, a rearm event expression.

One or more attributes can be used in an expression. Attributes can be a combination of dynamic and persistent attributes. Some examples follow.

The following expression generates an event notification if, during any sampling interval, the number of page-ins exceeds twice the number of page-outs. Note that the P suffix indicates the previous value. The RMC subsystem maintains the Nth and Nth -1 value of each monitored attribute.


(VMPgInRate@R - VMPgInRate@RP) > 2 * (VMPgOutRate@R - VMPgOutRate@RP)

The following expression generates an event when the file system is almost full, but the number of files in the file system is relatively small.


PercentTotUsed > 95 && PercentINodeUsed < 5

The following example uses PercentTotUsed in the primary expression and Size in the re-arm expression.


PercentTotUsed > 90

Size > Size@P && Size@P != 0

In this case, a "file system full" event is generated when the file system is greater than 90%, but the RMC subsystem does not start looking for that condition again until the file system has been made larger. The check for the previous value of Size is to handle the start monitoring case, where there is no previous value.