ipMonitor processes Alerts based on settings specified during Monitor configuration.

The parameters entered in a Monitor's Timing section allow you to intensify or lessen testing during each of a Monitor's four testing states: Up, Warn, Down and Lost.

Notification Control settings determine how many test failures must occur before an Alert is sent, as well as the maximum number of Alerts that will be sent.

Top of page

This example illustrates how Timing and Notification Control parameters affect the failure and alerting process.

Timing Settings :: Delays Between Tests While
Up	30 seconds
Warn	30 seconds
Down	60 seconds
Lost	30 seconds

Notification Control
Accumulated Failures per Alert	3
Maximum Alerts to Send	3

The table below outlines changes in Failure Count and Monitor State as the Monitor progresses from a Warn to a Lost state. A monitor will advance from a Fail to a Lost state when the maximum number of Alerts has been processed.

Failure Count	State	Action	Time Elapsed
1	Warn	None	0:00
2	Warn	None	0:30
3	Fail	Alert	1:00
4	Fail	None	2:00
5	Fail	None	3:00
6	Fail	Alert	4:00
7	Fail	None	5:00
8	Fail	None	6:00
9	Fail	Alert	7:00
10	Lost	None	7:30

Note: For more information on configuring a Monitor's Timing and Notification Control parameters, please refer to General Monitor Settings.

Top of page

Each Monitor has a Downtime Simulator menu option that will demonstrate the entire Alerting process from a configured Start Time and Duration. The primary purpose of the Downtime Simulator is to test Alert coverage for a Monitor at a specific time of day during any day of the week. It does this by processing every Alert that can be triggered by the Monitor across all Profiles.

Note: For detailed information on how the Downtime Simulator works, please refer to the section titled Downtime Simulator.

Top of page