The Ping monitor verifies that a specific computer or devices is available on the Internet. The default interval is set to 60 seconds.
ipMonitor measures the round-trip time by sending an Internet Control Message Protocol (ICMP) echo request to the specified IP address, and then waiting for a valid UDP packet to be returned. The test passes if the monitor receives a valid return packet within the required timeout period. The test fails if the monitor's specified timeout period expires.
The Ping Monitor tests the following:
- The route between the ipMonitor host machine and an IP-enabled computer device
- The target computer or device is able to respond
- The packet makes the complete round trip within a specific number of seconds
The Ping monitor is often used as a dependency for a group of monitors. For example, a web application group could include a web server, SQL server, drive space, and a Ping monitor that monitors the availability of the server computer.
In this example, you could assign the Ping monitor as a dependency for the web application group. If problems occur with the server, this configuration would prevent you from receiving alerts for all the application monitors and resource monitors configured to watch the server computer. This process would minimize the number of alerts you receive and help you identify the source of the problem.
Create a Ping monitor
- Click Devices in the toolbar.
- Locate and click the targeted device you want to monitor.
- In the toolbar, click Add > Add New Monitor.
- In the Select Monitor menu, click Ping.
Under Identification, enter a name in the Monitor Name field using up to 64 characters.
This name will appear in the Monitors List, Monitor Status, Logs pages, and your reports.
You can change this name later, if necessary. ipMonitor does not use this field to internally identify this monitor.
Select Enabled to enable the monitor.
When enabled, the monitor tests the specified resource using the settings you enter under Test Parameters. You can disable the monitor later if required.
(Optional) Select Store Monitor Statistics for Recent Activity and Historical Reports to enable this functionality.
Under Test Parameters, enter the IP address or domain name of the target server.
Under Timing, configure the fields for the monitor testing states.
- In the Maximum Test Duration field, enter the maximum test duration rate (in seconds) that the monitor times out before the test is considered a failure.
In the remaining fields, enter the number of second between each test while the monitor is in an OK state (Up), a failed state while alerts are processed (Down), and a failed state and the maximum number of alerts have been processed (Lost).
In the Lost state, no additional failure alerts are processed. However, a recovery notification is sent if the monitor recovers.
Under Notification Control, complete the fields to determine how many test failures must occur before an alert is sent.
- Enter the number of test failures that occur for each alert before ipMonitor generates an alert for the monitor. The default option is 3.
Enter the maximum number of alerts to send before the monitor enters a Lost state.
The monitor must be assigned to a notification alert to generate an action.
Under Recovery Parameters, complete the fields to indicate the corrective action used to automatically restore a resource using the External Process Recovery, Reboot Server Recovery, or Restart Service Recovery action.
- Enter the Fully Qualified Domain Name (FQDN), NetBIOS, or IP Address of the machine hosting the service that needs a restart or the machine that needs a restart. You can also click Browse to locate and select the machine.
- Select the set of credentials used by the recovery alert. You can select a specific credential to execute recovery alerts that require access to restricted resources, such as Reboot Server, Restart Service, or External Process.
- Select the list of services to restart on the target machine specified in the FQDN/NetBIOS/IP Address field. This field is only required for the Restart Service alert. If a service has dependencies, select all dependent services.
- Click OK.
Test the monitor
See Downtime Simulator for details about testing the monitor before you roll it out.