Action / Alarm Settings

Introduction:

This section is common to all the editions of IT360 - Professional Edition, Enterprise Edition [Probes only] and MSP Edition [Both Central & Probes].

This section explains the Action / Alarm Settings that can be made in IT360.

Configuring Action / Alarm Settings:

To configure the Action / Alarm Settings, do the following;

1. In case of Professional Edition and Enterprise & MSP Editions (Probe):

   • Go to 'Admin -> Servers & Applications -> Action / Alarm Settings'.

2. In case of Enterprise & MSP Editions (Central):

   • Go to 'Admin -> Notifications -> Action / Alarm Settings'.

Now, do the following in the Action / Alarm Settings page displayed.

3. General: Enable Action when alarms are generated (Checkbox)

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.

4. Repeat Action Executions:

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 first option is to enable a given action, when an alarm is generated. The types of recursive actions that are involved are;

• Availability: If a Monitor is down, you can execute actions repeatedly till the Monitor is up (Checkbox).

• Health:

  • If Health is critical/warning, you can execute actions repeatedly, till the Health is clear. Restrict the number of executions (set 1 for default value, or leave blank for unrestricted executions). (Radio button)

  • If the Health of the monitor is Critical/Warning, execute actions repeatedly, until it is Acknowledged/Picked Up (Radio button).

• Attribute Level: If the attribute status is Critical/Warning, then you can execute actions repeatedly, until it is clear (Checkbox).

5. EMail:

   • By selecting this option, you can add the Server Snapshot, as an inline attachment in the alert EMail. This option is available only if the Health becomes critical (Checkbox).

   • Another option available with email action is the Content Transfer Encoding option, during email content transfer [Dropdown values - base 64, 7 bit, 8 bit, binary, quotient-printable].

6. Monitor Error Mail:

You use this option when you want to send an error mail only after it occurs consecutively, say for 3 polls [poll instancecs is configurable].

• Send errors that occurred during monitors polling to admin user Email (Checkbox).
• You can also enter the number of consecutive polls, before sending error.

7. Date Format for $DATE replacable tag in Alarm:

By using this option, you can set the required date format in the Email alerts. 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.

8. SMS:

By default , the complete information, which 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.

Note: The term "SMS" refers to "Text message".

 

Consecutive Polls before Reporting an Error:

The Critical, Warning, and Clear alerts are generated based on attributes that you have configured. You have control over the alerts that are being generated. Simply specify the number of times after which the alert should actually be generated. It would eradicate false alarms.