Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > ipMonitor > Determine why an alert was not triggered

Determine why an alert was not triggered

Table of contents
Created by Chris Foley, last modified by Karen Valdellon on Apr 27, 2017

Views: 72 Votes: 0 Revisions: 5

Overview

This article provides steps to help investigate the issue where a monitor failed but no alerts were triggered.

Environment

  • All versions of ipMontior
  • All versions of Windows

Steps

  1. Log in to the ipMonitor web interface.
  2. Open the Settings page for the failed monitor that didn't trigger the alert.
  3. Click Downtime Simulator.
  4. Set the Downtime Start Time value to the weekday and the time when the failure occurred.
  5. Click Update.
  6. In the first light red box, note the actions listed (if any) and their values in the Queued column.
    • If the value is No:
      1. Click the action name. This will take you to the action's Settings page.  
      2. View the Availability calendar to verify that the time of failure is not excluded.
      3. View the Alert Range value to verify that it is not set to a value higher than 1 or 1-.
    • If the value is Yes:
      1. Close the Downtime Simulator window.
      2. Note the "id=" value at the end of the address in the browser address bar.
      3. Search for this ID in the following file to determine when the monitor went into a Down state (the only state where alerts are triggered) and what alerts were triggered:
        -\program files (x86)\solarwinds\ipmonitor\ipm{Date}.log  
        Where {Date} is the date the failure occurred.

 

Last modified
21:16, 26 Apr 2017

Tags

Classifications

Public