MonitorMagic - Tools4Ever.com

MonitorMagic
The rule is triggered for a period of time that exceeds the specified period.
The rule is not acknowledged.
See the topic on Escalation for more information.
... and the execution of action .... failed/succeeded
This option is used to execute an alarm action that is dependent on the result of the execution of
another alarm action. For instance, you might want to send an E-mail if a service is stopped and it
was not possible to start the service first. You can select the action for which this action is
dependent on from a list. The list shows all the names of alarm actions preceding this action.
Repeat action every ... minutes for ... times maximum.
Select this option if you want MonitorMagic to repeat this action. You can specify the frequency
and maximum number of times. Before MonitorMagic repeats the action it will check if the
rule is still triggered by re-evaluating the monitor values.
Rule no longer triggered
Select this option if the action must be executed when the rule was triggered but is no longer
triggered. The alarm action is executed only once when the rule is no longer triggered.
Rule not triggered
Select this option if the action must be executed when the rule is not triggered. The alarm action
will be executed each time the monitor is processed and the rule is not triggered, regardless of
the previous rule state.
Action disabled
Select this option to disable the action. MonitorMagic will not execute the action when this option
is selected.
See also:
Policies, Monitors, Rules and Alarm actions
Alarm actions overview
Activating the manage alarm action window
Alarm action name
Managing alarm action execution
Escalation
Keywords overview
Escalation
Escalation is a mechanism used for alarm actions: 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. The procedure is best
described by an 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 E-mail to your own E-mail
account.
To configure this scenario, you first create a performance counter monitor. For this monitor, you
create a rule that checks a value against some reference value. For this rule, you specify 2 alarm
actions:
The popup notification message. The alarm actions is configured to be executed
immediately when the rule is triggered.
136