 |
IPSentry - Alert - Add-In Alerts
The Add-In Alert tab provides you with the ability to
configure additional alert functions by incorporating third-party or in-house
custom add-ins which comply with the IPSentry Add-In Development Specification.
This tab provides the means necessary to Add, Edit, Remove, and Sequence add-in
alert functions to fit your requirements.
Please see the How-To section for additional
information on various configurations.
Enabled
This frame provides a tri-state selection regarding the status of the alert
which allows you to enable, disable, or use the global state (default)
Alert Success
All alerts with the exception of paging alerts make use of this setting.
When checked, the alert will be generated both when the system fails an when the
the failure is corrected.
For example, if you are monitoring a web server and it fails, the alert would be
triggered noting that there is a failure. Additional failure notification
will be sent according to the alert schedule outlined below. Once the
system is recovered and the failure corrected, another alert will be generated
as an "UP" notification.
In using alerts such as Pager or Email, the IPSentry Keyword %IPS_M_STAT% will
be converted to the current state of the device making it possible to recognize
immediately whether the alert was triggered due to the system going
"DOWN" or coming back "UP".
Each Add-In component contains it's own setting for the Alert Success option and may be set on an add-in by add-in basis. (eg. You would not want to trigger the NT Service Control add-in once the service is active as it would simply be a waste of time.)
Add-In (list)
This area contains a list of add-ins that will be triggered for the sentry item
selected. The order of add-ins within the list is displayed in the
sequence in which they will be triggered.
The list contains important configuration information such as the Add-In Name,
Alert Schedule, Success Alert setting and add-in args.
Add (button)
Click this button in order to browse and select from a list of Alert Style
add-ins currently installed on the system. Remember, only add-ins that can
be used for alerting will be displayed in this list even though you may have
other add-ins installed. (e.g. The File/Directory monitoring add-in will
NOT appear on the list from this area.)
Del (button)
After highlighting an add-in in the add-in list, hit this button to remove the
add-in from the list.
Config (button)
Hit this button to launch the Add-In General Alert Settings dialogue. From
this window you will be able to set the Alert Schedule and Alert Success values
as well as modify the add-in configuration settings either directly through
editing of the Add-In Args or through the add-in configuration utility.
See also: Alert Add-In Configuration
Up (sequence button)
After highlighting an add-in within the list, hit the arrow just below the
"Add" button to move the add-in up in sequence. Add-in alerts
will be triggered in the order they appear in the list.
Down (sequence button)
After highlighting an add-in within the list, hit the arrow just above the
"Del" button to move the add-in down in sequence. Add-in alerts
will be triggered in the order they appear in the list.
Load Defaults
(button)
This button will load the default configuration information into the appropriate
fields. This is a quick way to use a standard configuration with minor
variations between entries.
Note: You need NOT use this option when the enabled option is set to
"Default" since the replacement of the alert configuration with
default configuration values will be done automatically when the alert is
triggered. You need only use this button when the enabled option is set to
YES and you wish to slightly modify the default configuration and make the entry
specific to the monitored device to which this alert is related.
Test Alert (button)
This option will attempt to process the alert as configured. A message will be
displayed regarding failure or success of the alert generation.
Alert Add-In Configuration
After hitting "Config" for a selected add-in, you will be presented
with the alert add-in configuration window which provides access to the actual
add-in settings as well as the unique alert schedule that will be used for this
add-in.
The window will contain the following items:
Add-In Name
Displays the actual name of the add-in component being modified as defined within the add-in.Alert Success
See Alert Success setting above.Args
Add-In's may or may not accept "args" through the IPSentry Add-In Interface. Check your Add-In documentation for the format and content you should put in this field. This will vary between add-ins as much as command line argument vary from application to application.
As you will notice with many add-ins, the contents of this field very often resembles a command line.
With add-ins that provide a configuration interface, you will seldom have need to modify the contents of this field directly. As a matter of fact, if this field is edited incorrectly, the add-in may not function. We recommend using the "Add-In Configuration" button for all add-in configuration options in order to comply with the add-in designers syntax requirements for the args field. Again, check the documentation provided with the add-in component.Add-In Configuration (button)
Hit this button to launch the add-ins configuration / properties window used to configure the settings that should be used by this add-in. The properties available on that window will be unique to the add-in and should be explained in the documentation provided with the add-in.OK
Accepts the current settings and stores the results to the add-in alert list.Cancel
Cancels any changes made to this add-in configuration and returns to the add-in alert general settings tab.Alert Schedule
The alert schedule allows you "fine tune" the alerting functions to avoid unnecessary alerting during an extended failure. You may not want to be paged every single time a failure is detected after the first alert. You can use this schedule to set how many failures must be detected before the first alert. Set how many failures must be detected for each subsequent alert, and the maximum number of alerts you feel are adequate to obtain a response from specified personnel.
- First After [n] failures
Represents the number of sequential failures that must occur before the alert notification is processed. You can increase this value if you notice a large amount of false alerts being processed. On some systems, response times may not be consistent and a failure may be detected due to overhead at peak times. If the failure continues for this number of cycles, the alert will be processed.
- Every [n] failures
Once the first alert has been processed, IPSentry will only process the alert notification after this many sequential failures. In many cases, once a failed entry has triggered an alert, notification during every IPSentry polling cycle is not usually required.
- Max of [n] alerts
Enter the maximum number of times you want IPSentry to process the alert notification. A value of -1 - infinite. This counter is based on sequential failures without a single success.
Note: Setting the first-after or every values to any value less than 1 can have unexpected results.
SCREEN SAMPLES
|
|
||
| Contact: support@ipsentry.com | https://ipsentry.com | © 2006 by RGE, Inc. - All Rights Reserved |