IPHost Network Monitor supports different methods of automatic reaction to undesirable changes on the resources and systems being monitored. The alerts are tied to the monitors and are performed when a monitor transition to one of the problem states occurs or when monitor recovers from problem state, i.e. when performance or availability issue with monitored object has resolved.
One of the main tasks of the monitoring system is execution of alerts as the monitoring system's reaction to the appearance of performance and availability problems in the operation of resources being watched. Prompt and informative notification of a problem helps to substantially reduce the downtime of important resources, which as a result decreases the loss of work time of monitored systems and applications users and improves the effectiveness of administrator work.
The most of alerts is sending a message with information on the problem using various means (e-mail, instant messengers, SMS and others). Methods of reaction based on program start (local or remote via SSH) or SNMP SET provide additional possibilities. With the help of such alerts you can implement any method of reacting to a problem state: ranging from starting/stopping of a service on a remote machine to rebooting.
Alerts
In IPHost Network Monitor all alerts are gathered in one common list of alerts. All alerts are available for work with any monitor. The types of alerts are:
- Send mail. Sending an e-mail to persons concerned. Some variables may be used in the message template, such as $MonitorName, $CurrentState, etc., which allows for instance using one template for any changes of state.
- Send SMS. Sending SMS to mobile phones. Your mobile provider have to support e-mail to SMS service. Sending SMS using GSM modem or mobile phone will be implementing soon.
- Pop-up window. It is a standard balloon connected to the application icon in the system tray with the message about a problem (state change).
- Net Send. It is a similar standard window with a message, a standard dialogue with a message on a remote machine.
- Starting a program. Starting an executable file or executing the code of a script in a language supported by Windows Scripting Host. The path to the file and arguments should be specified.
- Sending Jabber message. Jabber is now wide spread, for example Google Talk is based on Jabber.
- Sending ICQ message. You should have ICQ account to use the action.
- Sending AOL message. You should have AOL messenger account to use the action.
- Play Sound. You can use any mp3 or wav sound files. Sound will be played if Windows client application are started or Alerts tab in Web interface are opened.
The full list of alerts is available for viewing and editing. To open the form with action list please select Tools from Settings menu (or Settings button on the toolbar) then select Alerts tab. It is important to remember that changes in an alert affect each Alerting Rule that uses the Alert.
Alerting Rules
In an Alerting Rule you link alerts to state changes. Also you can set a schedule for each alert in Alerting Rule, i.e. on which weekdays and during which hours alert should be on.
By default, a monitor uses the Alerting Rule from its monitor type. So you can easily manage alerts for the whole monitor type, for example, if it is necessary to add a new alert to all the monitors of the HTTP type, it can be done in one place without having to change the Alerting Rules in all the monitors of this type.
Description of other features
| Monitoring Features | Here you can find the list of monitor types supported in IPHost Network Monitor and brief description of their parameters. |
| Reporting Features | Here you can find the list of report types available in IPHost Network Monitor with brief descriptions. |
|
IPHost Network Monitor interfaces and structure |
Here you can find an overview of IPHost Network Monitor components, Windows and web interfaces. |
