Skip to main content
Nintex Community Menu Bar

Hi,

I am looking to exchange some notes related to the configuration of the Azure load balancer with K2 Five.

 

Specifically, the K2 farm can interact with users via multiple ports captured via:

https://help.k2.com/onlinehelp/K2Five/ICG/5.3/default.htm#Prepare/Firewall-Settings.htm

 

Outside of obvious ports 80 and 143, how can I configure Azure's load balancer to allow for monitoring and proper load balancing of other ports? Specifically, can I monitor and load balance ports 5555 and 5252?

 

Thanks a lot.

-BJ

Hi bjbier,


 


Maybe the Azure LB health probes can be used in your scenario, it sounds like you might have to create health page check for K2 servers.


https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-custom-probe-overview


https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-standard-diagnostics

Thanks. Azure's load balancer health probes, in this case, seem to be only scratching the surface - we've been running with these probes for a while, however, they fail to detect less frequent but more impactful outages, to be more specific k2 service down situations.  One thing I have not tried to do yet, was to design the health check page. Have you seen anything that could be used as a template? Do you have some ideas what to check for? 

 

Such a page would need to trigger K2 internals so that I'd not confuse IIS responses with responses caused by k2server. I'm sure I could try to reverse engineer some internal asps that are provided by K2, it's just a matter of time.

 

Thanks a lot!

 

Reply


Sidebar Buttons
Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
Terms & ConditionsCookie Settings