Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

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

Inconsistent HTTP binding component status

Created by Robert Stidman, last modified by Shane Horgan on Aug 30, 2017

Views: 103 Votes: 1 Revisions: 5



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


If the HTTP binding component fails during the initial poll, it is automatically soft-disabled (in comparison to hard-disabling, which can be a performance by the user. It is normally polled while in soft-disabled state. When the HTTP binding component succeeds for the first time, it will not go into soft-disabled state, from that point it will just go down.


  • 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