 |
IPSentry - Server Settings - Add-Ins
After selecting "Add-In" on the left
side of the "Server Settings" tab, you will have access to the
following fields for selection and configuration of installed IPSentry Add-In
components.
Please see the How-To
section for additional
information on various configurations.
Name
Select a short yet meaningful name to describe this monitor entry.
The name must be unique in order to identify this configuration from any other.
Also note that when IPSentry cycles through these items, the devices are ordered
alphabetically. Dependent machines are ordered within their respective
parent machines. Therefore, a system named AROUTER will be checked before
an item named CROUTER.
Description
Use this field to further describe this monitoring entry. A brief
description of the unit, device, etc. In many cases, this can be the same
as the name however it can be better used for various identification
purposes. This field must contain a value even though the value is used
only for various 'display' operations.
Add-In
This field represents the stored name of the Add-In and is read-only (you can
not and should not edit this value). The value placed in this field is the
name of the add-in selected after choosing "Browse Add-Ins".
Add-In Configuration (button)
If the add-in provides a configuration interface (as of this writing, all
add-ins provided by RGE, Inc. utilize a configuration interface), this option
will launch the configuration editor for that specific Add-In. You should
refer to your Add-In documentation for information on whether the add-in
supports Monitor Configuration.
Note: Do NOT hit this button before selecting an add-in using the
"Browse Add-Ins" button. You will receive a "Control
Creation" error if the add-in has not been selected.
Browse Add-Ins
This button will load a list of available Monitor type Add-Ins from which you
can select the add-in you wish to use. Unlike the image below, only
Add-Ins with a usage type of "mon" (monitor) will be available.
Note: Some add-ins are Alert Only or Menu Only type add-ins and they will not
appear in the list of add-ins available at this point.
Add-In 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. 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. Again, check the documentation provided with the add-in
component.
COMMON TO ALL MONITORING TYPES
Schedule (Button)
This will bring up the IPSentry Down-Time Scheduling tool and allow you to
specify what times during which days that this entry should or should not be
monitored.
(See Down-Time Scheduling )
Reverse Alert
In some cases, you may find it necessary to be notified when a server or network
device is available as opposed to unavailable. (I.e. Specific DHCP lease
activated, or a backup system has been enabled). By selecting this option,
a successful attempt on the device will trigger the alerts and a failure will
simply continue on to the next monitored device.
Suspend Sentry
Select this option to suspend this
monitoring option indefinitely. No monitoring or alerting will be
performed on this entry until the suspend flag has been removed. You can
easily identify suspended machines in the item list as identified by the yellow
triangular warning icon.
In version 4.6.55 and later, you are not prompted for the duration in
Days:Hours:Minutes. The release date/time is calculated from the moment
you hit "OK". Leaving the field blank or entering 0:0:0 will suspend the
item indefinitely.
Poll Frequency
Some systems require a more or less frequent monitoring. In order to
decrease network overhead, you scan select to have IPSentry skip a monitoring
entry for the defined number of cycles.
For example: If you enter a value of 5 in this field, IPSentry will have to
perform 5 full monitoring cycles before this entry will be monitored once.
If you have your Sentry Cycle Interval set to 5, that would be a minimum of once
very 5*5 or 25 minutes. Then, you must add-in the amount of time consumed
to complete an entire cycle and multiply that times this value.
Depends On
Provides a list of existing monitoring entries from which you may select one
that MUST be available (successful) before the current entry will be checked.
For Example: If Web1 is on the other side of Router1, there is no need to
check Web1 if Router1 is down. While editing the Web1 configuration,
you would select Router1 for this field. This would cause Web1 to be
skipped whenever there is a failure at Router1.
Sync Failure
Count
Checking this option keeps the Attempt + Failure counters synchronized among
dependents of specific machines. If the entry on which this item depends
is in a failure status, this item will be skipped yet the failure counters will
be incremented.
Example: If Web1 Depends on Router1 and Router1 fails, Web1 will also show as a
failure thereby reducing the up-time percentage.
Current
Dependents
This area lists all the monitoring entries that depend on the success of this
machine whether directly, or indirectly through another machine. This area
provides a basic tree-view of dependency information for the given device.
Add (button)
Use this option to quickly add direct dependents to this device by selecting the
entries from a list presented after clicking this button. Simply check the
items that will depend on the current machine and click OK.
Remove (button)
Use this option to quickly remove the selected dependent from this device.
Simply highlight the dependent that should no longer depend on the current
device and hit the Remove button.
Copy From (button)
This option loads a list of machines from which you can copy the entire
configuration. Very handy when you have several entries to create that are
all relatively similar in function (i.e. Adding 10 web servers where the only
difference is the IP Address, adding 25 routers with only the IP Address being
different.) (See Copy From )
Order Alerts
(button)
When you hit this button, you will be presented with the list of alerts in the
order in which they will be triggered. In some cases, you may want to have
fast alerts such as Email, Syslog, Launch, executed before the pager alerts.
In other cases, you may want pager alerts to be the first alert triggered.
Use this option to order the alerts to meet your specific needs. (See Ordering
Alerts)
Test (button)
This button simply tests the device monitoring configuration as entered.
You will either receive a "Sentry OK" response if no alerts would be
triggered based on the result of the test, or you will receive a
"Failed" message noting that in live operation, any configured alerts
would have been triggered.
This allows you test a known 'good' system to ensure that your settings are
correct.
SCREEN SAMPLES
|
|
||
| Contact: support@ipsentry.com | https://ipsentry.com | © 2006 by RGE, Inc. - All Rights Reserved |