Auto Balanced Collector Groups need a rework | Feature Requests

SeanC · 2021-09-22T01:37:14Z

Currently, if a collector goes down the devices it was monitoring will only failover to other collectors in the group if doing so does not put them over the defined Rebalance Threshold on the ABCG. This means you can't specify a Rebalance Threshold that allows instances to rebalance evenly across your collectors AND allow for instances to failover, it's one or the other which defeats the whole purpose and takes the Auto out of Auto Balance as to have collectors run in an n-1 highly available configuration means you have to specify a Rebalance Threshold value that is higher than the total instance count divided by the number of collectors minus one, then after a failover you have to adjust the Rebalance Threshold to a number close to the total number of instances divided by number of collectors, trigger a rebalance, wait, and then set the Rebalance Threshold back to total instance count divided by the number of collectors minus one. Madness! I propose keeping the Rebalance Threshold field but making it actually behave like it's name; when instance count is over the value, collector tries to offload instances to other collectors in the group. BUT, allow instances from a failed collector to offload to collectors past that threshold value so that failover continues to work. To address the concern of collectors being pushed past their capacity, add an additional field called Max Allowed Instances and only disallow instances to be offloaded to a collector if the instance count would push it past that value and trigger an alert in the event that that happens. This will allow us to have HA configurations AND auto balancing of instances work at the same time, as well as alerting us to the fact that instances have not failed over when it happens so that steps can be taken to increase the sizing/number of collectors.

MoreDiscussions

Auto Balanced Collector Groups need a rework | Feature Requests | LogicMonitor Community