Forum Discussion

sundogbrew's avatar
sundogbrew
Icon for Altocumulus rankAltocumulus
Feb 08, 2012

monitoring multiple ports on a host

So up until this point most of my health monitors have been pretty simple but I came across something today that may be a little more complex. Perhaps I am just over thinking it or thinking about it incorrectly.

I got this new application and the developer wants all the traffic from several applications sent to port 80 no problem there. But he wants me to monitor a different port to see if the service is up or not. He also wants me to monitor 80 and if it is down take the node out entirely. It is a group of servers that host a bunch of applications.

 

So my thoughts were to monitor http at the node level and monitor the other port at the pool level. Then I will need a pool for every different application and monitor the port he is using at this level and then send to port 80 anyway. If port 80 goes down I will remove the node from all pools, if the other port goes down the node gets removed from that pool. Sounds easy enough, but then at the node level you can't monitor http, it doesn't show up? Can you create a custom one that will do it that will show up in the monitors window at the node level? Then secondly at the pool level, can you monitor a port that you aren't sending traffic to? I always thought of the monitor as running on the port you are sending the traffic to? Am I on target or way off here?

 

As always, thank you for the help in advance!

 

Joe

 

 

 

management
monitoring
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Feb 09, 2012
    I got this new application and the developer wants all the traffic from several applications sent to port 80 no problem there. But he wants me to monitor a different port to see if the service is up or not. He also wants me to monitor 80 and if it is down take the node out entirely.why won't you assign two monitors to pool? one is for port 80 and the other one is for another port. 

    [root@ve1023:Active] config  b pool foo list
pool foo {
   monitor all http and mycustom
   members 200.200.200.101:80 {}
}
[root@ve1023:Active] config  b monitor mycustom list
monitor mycustom {
   defaults from http
   dest *:8888
}

    but then at the node level you can't monitor http, it doesn't show up?since node does not port configuration, monitor has to configure specific port such as mycustom monitor above.

    Then secondly at the pool level, can you monitor a port that you aren't sending traffic to?yes. mycustom monitor above is an example.
  • sundogbrew's avatar
    sundogbrew
    Icon for Altocumulus rankAltocumulus
    Feb 17, 2012
    Thanks so much for the response, not to be a tool, but how do I do that in the GUI?

     

    Joe
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Feb 20, 2012
    the alias service port (e.g. dest *:8888) will be shown if you change configuration in monitor config from basic to advanced.

     

     

    when configuring pool, availability requirement will be shown if changing configuration from basic to advanced too. this allows you to specify a number of monitor which must be successful to make pool member up.

     

     

    hope this helps.