Documentation forIpMonitor

ipMonitor monitor

The ipMonitor monitor is used to monitor an external ipMonitor installation on another computer. You can configure the monitor to perform internal diagnostics of an ipMonitor installation you specify, as well as perform redundant monitoring and alerting on behalf of an ipMonitor installation

You can also use the monitor to verify that a remote ipMonitor installation can accept incoming sessions, conduct transactions using the HTTP or HTTPS protocol, and respond within a required number of seconds.

Create an ipMonitor monitor

  1. Click Devices in the toolbar.
  2. Locate and click the targeted device you want to monitor.

  3. In the toolbar, click Add > Add New Monitor.

  4. In the Select Monitor menu, click ipMonitor.

  5. Under Identification, enter information about the monitor.

    1. Enter a name in the Monitor Name field using up to 64 characters. This name will appear in the monitor list, monitor status, log files, and your reports.

      You can change this name later, if necessary. ipMonitor does not use this field to internally identify this monitor.

    2. 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.

    3. Select Store Monitor Statistics for Recent Activity and Historical Reports to enable this functionality.

  6. Under Test Parameters, enter the monitor testing parameters.

    1. Enter the protocol used by ipMonitor to connect to the remote ipMonitor installation.
    2. Enter the IP address or fully qualified domain name (FQDN) of the resource you want to monitor.
    3. Enter the TCP port number that the targeted resource responds on. The default is TCP port 8080.
    4. (Optional) Select a credential for monitoring. When selected, ipMonitor uses the credential account and password information to authenticate to the target machine and test the bandwidth status.

    5. (Optional) Select Force communication through an HTTP Proxy Server to monitor the HTTP resource through your HTTP proxy server.

      Before you select this option, ensure that the ipMonitor global Client HTTP Settings selection in System Settings are set up correctly to allow communications with your proxy server.

  7. Under Analysis of Test Results, select the monitoring criteria to determine the Fail state of the remote ipMonitor installation.

    1. Click the Group Testing drop-down menu and specify which function the ipMonitor monitor will perform:

      • Do not obtain the status of a group, just a quick diagnostic
      • Fail if any group member or Dependency monitor is down
      • Fail if any group dependency is down
      • Fail if any group member is down

    2. If you did not choose a Fail if option, go to the next step and configure the Timing parameters.

      If you did choose a Fail if option, click Select and select a group on the remote ipMonitor installation you want to monitor for a Down state. ipMonitor will perform redundant monitoring and alerting for the external ipMonitor installation.

      If the Group list does not display, do the following:

      • Check the IP address or domain name by pinging and performing a traceroute to the remote ipMonitor installation. This will verify the connection.
      • Verify that the TCP Port is correct.
      • Log in to the remote ipMonitor installation to verify that the account you provided in the Account information field is valid and has real-time statistics list access.

  8. Under Timing, configure the fields for the monitor testing states.

    1. 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.

    2. 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.

  9. Under Notification Control, complete the fields to determine how many test failures must occur before an alert is sent.

    1. Enter the number of test failures that occur for each alert before ipMonitor generates an alert for the monitor. The default option is 3.

    2. 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.

  10. 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.

    1. 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.
    2. 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.
    3. 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.
  11. Click OK.

Test results

The test will fail and trigger an alert when:

  • The specified remote ipMonitor installation is unavailable.
  • The diagnostic fails to complete within the Maximum Test Duration.
  • Depending on the Group Testing option selected in the Analysis of Test Results section, a member or Dependency monitor in the selected group has tried to trigger an alert.