HTTPS monitor

I create https monitor to monitor my website example www.mydomain.com.

This wenbsite hosted in the cloud, then when i create the application monitor i assign mode-1 as test node.

When node-1 have internet connection issue why the SAM detect monitor to www.mydomain.com still up an running even i test manually using web browser and the page is can't be reached.

Find more posts tagged with

sam

https_monitor

Accepted answers

All comments

Lofstrand

Because the check is not done from Node-1, it's done from the SolarWinds server.

When a node is classified as down, it means that solarwinds can't reach it with ICMP Ping, that doesn't mean it can't be reached by other protocols, like https. So SolarWinds does not stop trying to poll all application monitors just because the node does not respond. (If you are using agents it might be a different situation).

Hope this helps.

hs08

if the check node is from orion server, so why we need to assign the monitor to specific node?

candersen159

Technically, you don't. That's just the Solarwinds dynamic. You're assigning the monitor to the node, so it know "what/who" to monitor; but application monitor can be set up to run remotely or locally.

If you wanted, you could set up a SAM application script that runs on the primary polling engine and kicks out (up to 10) variables; then set up alerts on those, and never add them as nodes.

I have https monitors setup specifically for external monitoring, then have other application monitors that run locally and examine processes on the server itself. I set the node name as <site.domain.tld>, then pass the node name as a variable into the built-in HTTPS monitor, so I don't have to customize a template/override every assigned monitor with each hostname. I'm sure there are other/better ways of doing it, but it got me started.

Ultimately, it sounds like you're having a problem due to how you set up the SAM monitor - is it checking just to see if port 443 is open, or if server:port is returning a webpage?

Like Lofstrand said - if you're just monitoring if you can *reach* the server - that's just a ping check, which won't tell you if the site is down or not.

It might also get more complicated if you have something like a Web Application Firewall or other proxy returning a valid website, but it's actually just an error page telling you the site is down. But if you're only checking for <is there a website at this address> and the WAF always returns either the page or an error page, then your validation needs to account for that.

How to Setup HTTP/HTTPS Monitor in SAM is super basic and won't really handle really complex scenarios.

Edit: Try: Monitor a specific URL in SAM instead.