NimbostratusI have a tcp monitor who's Alias Service Port is set to 1414, but the service port is still displaying 1883. For the pool(s) that this monitor is monitoring, is it actually monitoring port 1414 or port 1883? Does the Alias Service Port of 1414 override the service port of 1883? Thanks!
Hank
EmployeeYes. The alias service port in the monitor should override the service port(s) in the assigned pool.
NimbostratusI have a follow-up question to this. What if i just want to use the alias port in the monitor for just health checking? What if I still want to pass the traffic to the pool member using the service port I used for the node? Is there a way to do this?
EmployeeWhat if i just want to use the alias port in the monitor for just health checking? What if I still want to pass the traffic to the pool member using the service port I used for the node? Is there a way to do this?
that is exactly how it works i.e. monitored port is the alias one. service port is the one defined at pool member.
NimbostratusOk I might have been confused by Kevinb Stewart's answer above where he says the alias port overrides the service port. When he says it overrides the port I woukd take it he means the port used for TCP monitoring only. Thanks!
NimbostratusWere any of you able to accomplish this via the iControl API by any chance? I'm hitting what seems to be a bug where if I try to set the alias service port to e.g. 80 on pool that uses 443, it will default to 443. This only occurs via my automation. Setting the alias service port via GUI work properly.