Hi All,
When we create an HTTPS monitor to check a URL. Please inform the bellow
The availability of URL is checked at Orion Poller or at assigned node
To access the URL, the DNS resolution occurs at Orion Server or at assigned node
We have two lab episodes on component monitors:
Plus a Lab Bits on it:
SolarWinds Lab Bits: Configuring the HTTP Form Component in SAM - YouTube
SolarWinds Lab Bits: Configuring the HTTPS Component in SAM - YouTube
SolarWinds Lab Bits: Configuring the SAM Web Link Component - YouTube
You can choose to assign it on the node or not, but assigning it to the node that hosts that website makes it a bit easier to know that if this website is down then thats the node where you need to fix the problem. When you assign the monitor it also defaults to trying to connect to that node's IP on 443, but you could over ride that and tell any monitor on any node to check any website if you want, but then it might get a little confusing.
This may be wildly late from the original post, however, It doing netstats on the node and the orion server, but mesverrum is correct, the poller is the Orion Node not the Agent that the component monitor is assigned to. This is unfortunate because I was hoping to use one template to monitor from multiple nodes.
I spoke too soon, look like you can set agentless or agent monitored.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.