Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > Alert was not triggered in ipMonitor

Alert was not triggered in ipMonitor

Table of contents

Updated September 21, 2018

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

Tags

Classifications

Public