MonitorMagic
Server Monitoring Solution

Alarm Options

Alarm Escalation:

In MonitorMagic, escalation is supported by means of un-acknowledged rules and specific alarm action settings. With MonitorMagic, detected problems can be escalated when they are not solved or taken care of.

Example: Suppose you want to monitor a critical system. When the system is overloaded, (CPU-load too high) a monitor rule is triggered. Notifications will be sent to the local Administrator of the system. If within 60 minutes, the problem still exists and no one has taken care of the problem, you want to escalate the problem and send an email to your own email account.

Email:

MonitorMagic supports SMTP email notification for real time monitoring of critical server and network statues. With SMTP email support network administrators can send email notifications on critical monitoring event, such as low disk space, service stop, and security event message.

Event Log Message:

MonitorMagic can send detailed messages to the application event log of the server running the MonitorMagic service. Each event can contain any number of keywords for enhanced event log messages.

Popup:

MonitorMagic supports sending detailed popup messages as alarm notifications.

Terminate Process:

MonitorMagic supports terminating process as an alarm action.

Examples:

Terminate target process - all process instances with process name
The target of this action is taken from the process specified in a Process monitor. If the computer has multiple processes (instances) running with the same name as the process monitor, all the processes with this process name will be terminated.

Terminate target process - target process instance only
The target of this action is taken from the process specified in a Process monitor. The process monitor corresponds with exactly one process (if the process is running). This process is identified by the process name and process ID. Note that multiple processes with the same name but different process ID's can exist on the computer. If you select this option, only the target process will be terminated.

Terminate specified process of target computer
The target of this action is not taken from the process(s) specified in a Process monitor. A Process monitor can contain settings to monitor multiple processes and you may not want to terminate all the processes contained in a monitor when it becomes triggered, this is when you would select this option. It is also possible that you may want to terminate a process on a machine other than the one being monitored; you would use this option under those circumstances as well.

Server Reboot:

MonitorMagic supports Shutdown or Reboot Computer as an alarm action.

Example: MonitorMagic is monitoring the IIS service on a server and detects in real-time that the IIS service has stopped. MonitorMagic first alarm actions is to start the service. If that alarm action fails MonitorMagic sends an email to the support team. If after 10 minutes the service is still down MonitorMagic will reboot the IIS server (Requires Alarm Escalation to be set).

Alarm Escalation: In MonitorMagic, escalation is supported by means of un-acknowledged rules and specific alarm action settings. With MonitorMagic, detected problems can be escalated when they are not solved or taken care of.

Stop + Restart Service:

MonitorMagic supports Stopping and Restarting Service as an alarm action.

Example: MonitorMagic is monitoring the IIS service on a server and detects in real time that the IIS service has stopped. MonitorMagic first alarm actions is to start the IIS service. Then 10 seconds later start the World Wide Web Publishing service and then the Simple Mail Transport Protocol (SMTP) service.

Pager + SMS:

MonitorMagic can send a message to a pager or mobile telephone (SMS). This is done by using a modem, connected to the server that runs the MonitorMagic service. The pager - SMS messages are sent by the MonitorMagic service depending on the configured alarm actions.

General operation

The following list describe the actions executed by MonitorMagic service and provider when sending a pager - SMS message:

• A monitor is checked by the MonitorMagic service. A monitor rule is triggered and pager - SMS alarm action must be executed.
• The MonitorMagic service queues the pager - SMS alarm action.
• The MonitorMagic initializes the connected modem and calls the configured pager - SMS provider.
• When the connection is setup, the MonitorMagic service instructs the provider to send a message to the specified pager - mobile telephone number.
• MonitorMagic terminates the call with the pager - SMS provider and is ready to send the next pager - SMS message.
• The pager - SMS provider sends the message and the pager or mobile telephone receives the message.