Should health monitor be the port on the node?
Is it the common practice to have the health monitor as the actual service (protocol) that is listening on the node its self?
So, for example if I have a server listening on port 443, then if I put the health monitor on 443 and the server isn't responding then I know for sure it has a problem with 443 on the server, correct?
Also, if I monitor the pool does that include all nodes in the pool? Or should I monitor the nodes individually?
I'm trying to create a custom monitor for UDP 3389 for a member in a pool. I want to monitor that port 3389 is always up and responding but I don't know what to put in the Send String or Receive String. The Send String has "default send string" already typed in the box.
Is it also possible to get notified when a service cant be reached? Thanks.