Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Alerts not triggered for IIS application pool

Alerts not triggered for IIS application pool

Updated December 15, 2017

Overview

SAM alerts were not triggered for an IIS application pool for a website that was down. 

Environment

  • SAM 6.0 and later

Cause 

This issue can occur if two websites are connected to the same server but one is up and the other is down. The IP address for each site on the server is identical but the "Host" header property specifies a different folder for each virtual website. When SAM checks the IP address and detects that a website is functioning, it will not generate an alert.

Resolution

To determine the status of different websites on the same server, use the following PowerShell scripts to simulate responses from a server. Replace variables with website URLs, as necessary:

For site "website URL A":
$Request = [Net.HttpWebRequest]::Create('http://IP ADDRESS/')
$Request.Host = "website URL A"
$Request.GetResponse()

For site "website URL B"
$Request = [Net.HttpWebRequest]::Create('http://IP ADDRESS/')
$Request.Host = "website URL B"
$Request.GetResponse()

 

 

Last modified

Tags

Classifications

Public