Generate alerts and notifications

ipMonitor uses a background process called a monitor to verify that a resource on a device is operating within a predetermined range. The resource can be any monitored statistic you enable on the device, such as physical memory, CPU, or device disk utilization.

When the resource reaches a critical range (for example, 95% CPU utilization), the monitor displays this information in the Dashboard. If you perform multiple roles within your organization and lack the resources to monitor all of your devices in the ipMonitor web user interface, you can configure ipMonitor to send you an email, text message, or another supported notification when a monitor reports a problem. This notification is called an alert.

About alerts

An alert is a collection of actions that act on behalf of a set of monitors. Administrators and departments can watch specific monitors and determine when and how they are alerted of monitor failures using alerts.

The alerts and suite of actions provide the required flexibility to accommodate many different types of notification methods and recovery actions.

Using the alert features, you can:

  • Configure each alert to be responsible for a single monitor, multiple monitors, or groups or monitors
  • Create any number of actions within each alert
  • Schedule each action independently
  • Specify escalated actions as problems remain uncorrected

If the action occurs during normal business hours, notify the administrator first, and then attempt to resolve the problem using a recovery action (such as rebooting the server or restarting a service).

If the action occurs outside of normal business hours, attempt to fix the problem using a recovery action, and then contact the administrator if the recovery action fails.

How alerts work when a monitor detects a problem

When a monitor detects a problem (for example, the quality of service has degraded, a predefined threshold is passed, a specific content pattern is detected, or a connection failure occurs), the following events occur in sequence:

  1. Each alert is scanned to locate the alert assigned to the failed monitor and to the groups that include the monitor.
  2. The Alert Range is checked for each action within the alert to determine if the alert should be triggered.
  3. The Alert Schedule is checked to determine if the action is active for the current time period.
  4. The selected notifications for the alert are sent. If notifications are not selected, the action does not occur.

Escalating alerts

ipMonitor supports escalated alerting. By controlling the number of monitor failures allowed to accumulate before triggering each action, you can share alerts with administrators in different areas of responsibility, between various recovery actions, or both.

Scheduling alerts

Each action supports an independent schedule based on a week-long calendar. You can configure the time periods in 15-minute intervals.

Credentials

You can set different credentials for each action. This allows you to use specific credentials when executing certain actions that require authentication. Actions can also use the Windows account assigned to the ipMonitor service as their credential.