From the Device Editor Main, select to Add or Modify an entry.
After selecting "Drive Space" in the Type selector, you will have access to the following fields for configuration.
Drive Space Monitoring Type Specific Entries
Enter either the drive [x:] or the network share name (in UNC format of \\servername\sharename\path) you wish to have IPSentry monitor.
The user under which IPSentry is running should have rights to read the directory information on remote system. If this is not the case, you will need to enter user credentials that will allow IPSentry connect to the remote system and obtain directory information.
Note: Because two users can not be logged into the remote system at the same time from the same machine, drive space failures may occur if IPSentry is running under one security context and a user logs in and connects to the remote system under another. To avoid this issue, you can specify the IP Address or the fully qualified domain as the computer name in the UNC.
For example: \\remotecomputer.mydomain.local\sharename instead of \\remotecomputer\sharename
Note: In some cases, a UNC Share Name can not be used and requires a mapped drive letter. In version 5.75 forward, you can specify that IPSentry first map a local drive to the UNC share by prefixing the UNC share name with <MAP> or <MAP x:> command.
In the drive space monitoring UNC field where you currently have \\server\c$\share\volume, prefix the value with "<MAP>" (including the angle brackets)
Run a test.
One problem you may run into is that some cdrom drives and other locally attached devices consume a drive letter but do not properly report the drive letter as "in use".. This would cause windows to return that drive letter as a free drive letter and when IPSentry mapped it, it would return zero bytes.
If you experience this problem, you can define a specific drive letter to be used with the mapping. However, this drive letter must never be mapped in the same session as IPSentry is running. It must be unused because IPSentry will not attempt to remap any drive letter that is already mapped.
To do this, you would change <MAP> to <MAP x:> where x: = the drive letter you wish to use.
Example: <MAP r:>\\servername\c$\path\path this would require that drive R be free and will map the specified folder to that drive.
If you are checking a network share, IPSentry will attempt to login under the security context of this user. Appropriate permissions must be granted. When running IPSentry as a system service, you should set the service to run as Administrator.
If you leave the User Name and Password fields blank, IPSentry will attempt to connect under the security context of the user under which IPSentry is running.
Enter the password associated to the Logon As account specified.
Launches a browse window from which you can select a drive or network share to monitor. This tends to be much simpler and more accurate that manually typing in the UNC.
Enter the minimum number of megabytes or gigabytes that must be available on the specified drive or volume. If the available space falls below this specified value, any configured alerts will be triggered.
Select the drive space scale in MB or GB to define the value of free space as either being free megabytes or free gigabytes.
Select from the 6 category types of monitoring entry you wish to edit.
RGE currently provides 6 primary categories with many sub types within each entry category creating a well rounded arsenal of monitoring functionality.
The categories and types of entries, with their sub-types are as follows:Group / Template
This entry type does not perform any actions or monitoring tasks on it's own. The Group/Template type is used for grouping of entry items as well as configuration of standardized templates, schedules, and alerting configurations.
[ Details ]
This entry type allows for TCP/IP based connection and data send/receive capabilities. There are currently 16 pre-configured standard ports and the option to utilize custom port numbers for the host entry. This is one of the most often used types of monitors within IPSentry.
[ Details ]
RADIUS * Deprecated - use the UDP/DNS/RADIUS Add-In
DNS-TCP * Deprecated - use the UDP/DNS/RADIUS Add-In
DNS-UDP * Deprecated - use the UDP/DNS/RADIUS Add-In
https * Deprecated - use the HTTP/s Web Monitor
This entry type will query local and remote system services to insure they are running. You may specify one or more services to be monitored within a single entry. However, you should be aware that if you are monitoring 5 services and one fails, the entry will be reported as failed. While detail information will be available as to the service that caused the failure, all alerts will be performed as a single failure.
[ Details ]
Drive Space Monitor
This entry provides local and remote drive space monitoring to insure that drive space remains above the user-defined low-water mark. In the event free space falls below your defined threshold, the defined alerts would be triggered. For monitoring multiple volumes, you should utilize the Performance Monitoring Add-in to monitor logical drive space percentages available.
[ Details ]
The back-reference monitor is new to version 5. This option allows you create an entry whose result is based on the state of one or more other entries in the system. You define the importance of each entry to be referenced (a weight) and define the maximum weight value that is acceptable. Thus, you can effectively create an entry that triggers alerts if (x) number of items are in a failure state.
[ Details ]Normal state is [Failure]
Database Connection and Query Monitor
Monitor databases and data sources for connectivity and query result capabilities.
Monitor DNS, RADIUS, and other UDP based servers.
Event Log Monitor
Monitor local and remote event logs for event messages of interest.
File & Directory Monitor
Monitor files, folders, sizes, counts, etc..
File Content Monitor
Evaluate file contents and trigger alerts when data is found.
HTTP/s Enhanced Web Monitor
Provides enhanced web server monitoring capabilities.
IT Environmental Monitor
Monitor Sensatronics environmental monitoring equipment.
Mail Transaction Monitor
Monitor mail delivery from relay host to mailbox for slow or non-delivery issues.
Modem Connection Monitor
Monitor ability to connect to remote dialup systems via modem.
MRTG Counter Value Monitor
Monitor MRTG HTML counter data values for critical levels.
Network Time Monitor
Monitor and Synchronize local time with network time servers.
Performance Counter Monitor
Monitor local and remote windows performance data counters for critical levels.
POP3 Mail Queue Monitor
Monitor POP3 mailboxes for message wait times and message content.
Scripted TCP/IP Network Monitor
Advanced network monitoring using scripted SEND/RECV Scripting
SNMP Object Monitor
Monitor SNMP compliant devices and systems for critical values, changes, etc.
If this entry is checked, then IPSentry will expect that the result is intended to be Critical. This is intended where you require a CRITICAL state to be returned for the entry to be successful. For example, let's say that you are scanning a file using the file content monitoring and want to be notified if it does not see the text "OK" in the file. By default, the file content monitor returns CRITICAL when it finds the expected text. In your case, you only want to be critical if it doesn't find that text. This would be a good case for enabling this option. Thus, configured alerts would only be triggered when the text was NOT found.
Enter a unique device name for this entry. The recommended device name entry should be brief yet descriptive. This name will be used in the statistics reporting, graphing output (if enabled), as well as textual alerts and notification where configured with the %%mach.name%% keyword.
Enter a meaningful description of the entry providing additional information about what and why the entry is being used and perhaps what is expected.
Click this button to modify the entry availability schedule.
This field shows the item upon which this entry is dependent in order to run. If the dependent item is in a Critical state, this entry (and by reference - it's children) will not be monitored. This is useful in group scheduling functions as well as avoiding monitoring of items that you know will be un reachable. For example, if you have 5 web servers on the other side of ROUTER A, you would set each of the servers dependent upon ROUTER A. If ROUTER A is down, it may be futile to try and connect to the web servers since we already know the link has an issue. Thus, ROUTER A would trigger it's alerts as the failing point, and the children would be skipped.
Synchronize Dependency Counters
In some cases, you may want the failure counters of child entries to reflect those of the parent. As in the above scenario, you may want to show that the 5 web servers dependent on the router have also failed. While the actual state of the web servers themselves is unknown, it is known that access to those servers is unavailable and perhaps this failure should count against them just as it does the router. Selecting this option is only used for basic statistical purposes and is not reflected in graphing details. Within the graphing details, if the item was not monitored, there will be no data for that time period.
Suspend / Resume MonitoringCritical Poll Frequency
Click this option to suspend (or resume) the current entry. When suspending a device, you will be presented the option of the duration for which the device should be suspended. You can enter the duration in DAYS:HOURS:MINUTES to suspend for a specific duration at which point monitoring of the selected entry will resume. If you leave the duration field blank or set to 0:0:0, the entry will be suspended indefinitely.
When suspending indefinitely, you must Resume the entry manually.
If you click the Select button at this point, you will be given the option to enter a specific date and time on which the entry should resume.
Normal Poll Frequency
This value represents the number of IPSentry cycles that must occur before the item is polled. The value is useful for monitoring items that may not need to be checked with as often as other items. For instance, connectivity to a network device such as a web server may need to be checked every 15 seconds where as checking drive space or scanning for an event log may only need to be performed every 5 minutes. In this case, you can set your sentry cycle interval to 15 seconds and set the poll frequency on your drive space monitor entry to 20.
This value represents the number of IPSentry cycles that must occur before the item is polled when it is in a CRITICAL state. This is useful for entries that have a high poll frequency under normal situations, but may have a tendency to auto-correct within just a couple of cycles thereby becoming stable. Setting this value to a lower value than the normal poll frequency allows for notification or recovery actions to be performed more quickly.
Click this button to copy the configuration settings from another entry. You will be presented with a list of existing devices from which you can copy the complete configuration.
Click this button to copy configuration specific settings from this entry to multiple entries. You will be presented with the Copy To dialogue in order to select the configuration properties to copy and a list of entries to which to copy the selected settings.
Click this button to set the preferred order of alert/notification. In some cases, you may want your email notifications sent before the pager notifications or vice-versa.
Simple highlight the alerting method and click the up/down buttons to reorganize the alerting sequence.
Click this button to test the configuration as it would run during a normal cycle. Note that this will not trigger alerts - rather, it will simply tell you the result of the configuration settings.
The result of the test will be displayed in the testing results dialogue.