If multiple sensor states are available for a specific sensor, the PXE asserts a state for it whenever a bad state change occurs.
To assert a state is to announce a "worse" new state. Below are bad state changes that cause the PXE to assert.
1. above upper warning --> above upper critical 2. normal --> above upper warning 3. normal --> below lower warning 4. below lower warning --> below lower critical |
In the threshold setup dialog, the Assertion Timeout field impacts the "assert" action. It determines how long a sensor must be in the "worse" new state before the PXE turns on the "assert" action. If that sensor changes its state again within the specified wait time, the PXE does NOT assert that state.
To disable the assertion timeout, set it to 0 (zero).
Note: For most sensors, the measurement unit in the "Assertion Timeout" field is sample. Because the PXE measures each sensor per second, a sample is equal to a second.
If you have created an event rule that instructs the PXE to send notifications for assertion events, setting the "Assertion Timeout" is helpful for eliminating a number of notifications that you may receive in case the sensor's reading fluctuates around a certain threshold.