Appendix E: Additional BCM2 Information
In the threshold settings, the Assertion Timeout field postpones or even
cancels the "assertion" action. It determines how long a sensor must
remain in the "worse" new state before the BCM2 triggers the
"assertion" action. If that sensor changes its state again within the
specified wait time, the BCM2 does NOT assert the worse 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. Sensors are measured every second, so the
timing of a sample is equal to a second. BCM2 is an exception to this,
with a sample of 3 seconds.
How "Assertion Timeout" is helpful:
If you have created an event rule that instructs the BCM2 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 readings fluctuate around a certain threshold.
Assertion Timeout Example for Temperature Sensors
Assumption:
Upper Warning threshold is enabled.
Upper Warning = 25 (degrees Celsius)
Assertion Timeout = 5 samples (that is, 5 seconds)
When a temperature sensor's reading exceeds 25 degrees Celsius,
moving from the "normal" range to the "above upper warning" range, the
BCM2 does NOT immediately announce this warning state. Instead it
waits for 5 seconds, and then does either of the following:
• If the temperature remains above 25 degrees Celsius in the "above
upper warning" range for 5 seconds, the BCM2 performs the
"assertion" action to announce the "above upper warning" state.
• If the temperature drops below 25 degrees Celsius within 5 seconds,
the BCM2 does NOT perform the "assertion" action.
To Next Page
Loading...
