Printer monitor

The Printer monitor uses the Host Resources MIB to retrieve statistics. You can use this monitor to alert on the following conditions:

  • Low resources, such as low paper or toner
  • Hardware malfunction, such as a paper jam or printer offline
  • Maintenance service, such as service requested or overdue preventative maintenance

Create a Printer 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 Printer.
  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. Click the Communication Type drop-down menu and select the process used by ipMonitor to connect to the printer.
    2. Enter the IP address or fully qualified domain name of the printer you want to monitor. For example:

      10.20.30.11

      www.example.com

    3. Enter the UDP port that the target printer responds on during a query. This field may be automatically populated for you based on the communication type you select.
    4. Click the SNMP Version drop-down menu and select the version used by the monitored printer.

      Both ipMonitor and the target printer must use the same SNMP version.

    5. (SNMP communication type) In the Community field, enter the common word or identifier used with SNMP devices. This is usually a requirement of most recovery scripts.
  7. Under Analysis of Test Results, select the printer issues and alerts you want to monitor on the printer.

  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.