Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Inconsistent HTTP binding component status

Inconsistent HTTP binding component status

Created by Robert Stidman, last modified by Shane Horgan on Feb 14, 2018

Views: 1,517 Votes: 1 Revisions: 6



This article briefly discusses some inconsistent behaviour some users may notice with Appinsight for IIS HTTP, HTTPS & SSL Certificate Bindings monitors. 


Examples of Inconsistent behaviours:

  • HTTP & HTTPS bindings components in AppInsight for IIS is disabled in the component details page but is enabled in the application monitor view.
  • Another symptom of this issue can be when users upgrade SolarWinds SAM Appinsight HTTP & HTTPS component monitors which prior to the upgrade reported as Up 


SAM 6.0 or later


Within Appinsight for IIS If the HTTP, HTTPS or SSL Bindings component(s) fails during the initial poll, these components are automatically 'soft-disabled' (in comparison to being hard-disabled, which can be a performed by the user). 


It is polled as normal while in a soft-disabled state but we will mark responses such as '401, 403 etc' as valid responses from the website to ensure it is marked as up for alerting & reporting purposes within Solarwinds. 


When the the above components initial poll is a success , it will be polled as normal from that point on & it will just get marked as down if we receive a response code such as '401, 403 etc'.


So in Summary:

  • If an HTTP (HTTPS, SSL Bindings)  binding component fails during an initial poll, it is automatically “soft disabled” (in comparison to “hard disabling” which can be performed by the user directly from the 'edit application monitor page') in order to prevent this monitor affecting the overall Application Status. 
  • It is polled as normal while being “Soft disabled” but HTTP Response codes such as "403 Forbidden, 401 Unauthorized, etc" are treated as a valid response. 
  • If an HTTP (HTTPS, SSL Bindings) binding component succeeds for the first time, it will not be put into a “soft disabled” state. If a monitor fails after this point it will get marked as down as this is no longer a valid and expected response from this website. 


If after an upgrade or install a hot fix you notice that these new 'down' responses are being recorded for the HTTP, HTTPS and SSL Bindings Monitor within your Appinsight for IIS application monitor it is possible to soft disable these monitors by following the steps in the below linked Knowledge Base Article - Disable the HTTPS Bindings Monitor in AppInsight for IIS




Last modified