Submit a ticketCall us

Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at customersuccess@solarwinds.com

 

 

 

 

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 MindTouch on Jun 23, 2016

Views: 787 Votes: 0 Revisions: 4

Overview

This article aims to help investigate the root cause of an issue where a monitor failed but no alerts were triggered.

Environment

  • All versions of ipMontior
  • All versions of Windows

Steps

  1. Login to the ipMonitor web interface.
  2. Open the Settings page for the Monitor that failed but no alerts were triggered.
  3. Click the Downtime Simulator.
  4. Set the Downtime Start Time value to the weekday and the time when the failure occurred.
  5. Click Update.
  6. Within the first light-red box, note the Actions listed (if any) and their value in the Queued column.

 

If the value is "No"

  1. click on the Action's name. This will take you to the Action's Settings page.  
  2. View the Availability calendar to ensure that the time of failure is not excluded.
  3. View the Alert Range value to ensure 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's address bar.
  3. Search for this ID within 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
19:34, 22 Jun 2016

Tags

Classifications

Public