ManageEngine® Applications Manager
Action / Alarm Settings
This section explains the Action / Alarm Settings that can be made in Applications Manager. To access Action / Alarm Settings, click the Admin tab and click Action / Alarm Settings.
When alarms are generated, actions are triggered for those alarms (if you have configured any). If you do not want the actions to be executed in spite of the alarms, deselect this option.
If you want the actions to be trigged continuously during every poll, till alarms change from Critical/Warning to Clear, you can use this functionality. The three types of recursive actions that are involved are
If a Monitor is down, you can execute actions repeatedly till the Monitor is up.
If Health is critical/warning, you can execute actions repeatedly till the Health is clear.
If the attribute status is critical/warning, you can execute actions repeatedly till the attribute status is clear.
By selecting this option, you can add the server snapshot - Dial view as an
inline attachment in the alarm EMail. This option is available only if the Health
By selecting this option, you can send emails in case of any fatal monitor error like data collection not happening, etc. This mail will be sent to the email address specified in the 'admin' user account. If no email address is specified, the mail will be sent to the email address specified in the 'Mail Server' settings, hence ensure that you specify a valid email address.
Furthermore, you can specify the number of times the error has to occur before email is triggered in the Check for consecutive polls before sending error box.
Using this option, you can set the required date format in the Email alarms.
It can either be
Day Mon dd HH:mm:ss IST yyyy (Default) - Thu Feb 22 12:02:40 IST 2007
MM/dd//yyyy HH:mm:ss - 02/22//2007 12:02:40. See Replaceable tags for usage of $Date.
By default , the complete information that you configure while adding SMS Action is sent through the SMS. Some SMS service providers restrict the length of characters sent through the SMS. This could result in truncated message delivery. If you would want to send only information on the Monitor, Attribute, and its Severity, deselect this option. For E.g., "Health of JBoss Server is critical" will be the SMS format that is received.
This is in addition to the message provided when creating the SMS action.
The Critical, Warning, and Clear alarms are generated based on attributes that you have configured. You have control over the alarms that are being generated. Simply specify the number times after which the alarm should actually be generated. It would eradicate false alarms.
If you want to poll '3' times before reporting that a system (or any Monitor) is down or an attribute is critical, specify the value as '3' in the first text box. Similarly, you can change the remaining two text boxes (warning, Clear) also. If you have set the poll as '2' times before reporting a service is up, for the first time of polling, the service will be shown as Unknown. Only on the second poll, if the service is running, the status would be shown as 'Up'. Changes made will be reflected across all the monitors.
Apart from Action / Alarm settings, Polls before reporting an error, can be configured for threshold and availability of individual monitors. Refer Configuring Consecutive Polls.
Windows Event Log Rules