Forum Discussion

Issac's avatar
Issac
Contributor III
17 days ago
Solved

Automatic Rebalance of collectors

There is any plans from SL team to make automatic rebalancing of collector groups in certain interval  like 24 hrs once.? As of now its needs a manual intervention.

  • Hello Isaac,

    This is stored in the meta_stats.dev_stats_rollup_hourly database table on the CDB. The avg_usage_count parameter is the value used during the rebalance.

    Antonio Andres

    Senior Technical Support Engineer | ScienceLogic

8 Replies

  • Issac's avatar
    Issac
    Contributor III

    Hi Andres,

     

    Thanks for detailed explanation , By anyway we can see those scores in DB ? Because some time when i manually do a rebalance the devices moves to other collectors.  

    • TonyAndres's avatar
      TonyAndres
      Icon for Moderator rankModerator

      Hello Isaac,

      This is stored in the meta_stats.dev_stats_rollup_hourly database table on the CDB. The avg_usage_count parameter is the value used during the rebalance.

      Antonio Andres

      Senior Technical Support Engineer | ScienceLogic

  • Issac's avatar
    Issac
    Contributor III

    Hi Eric  - During every device onboarding the i don't think the SL checks the collector load and maps into collector accordingly based on load . I always see one are other collectors have higher count always and it required manual reblance.

    • TonyAndres's avatar
      TonyAndres
      Icon for Moderator rankModerator

      Hello Isaac,

      The CUG rebalance is not based on device count, but rather each device is assigned a score internally. This score is calculated based on the total number of dynamic apps aligned to the device and how many actively monitored interfaces the device has, and the final score is whichever of these 2 values is highest which then becomes the device rating. It then calculates the collector's load, which is the sum of all of the device ratings for the devices aligned to the collector. During a CUG rebalance, SL1 tries to spread out the load evenly based on the device rating and the current collector load. The rebalance will also be affected by whether or not collector failover is enabled in the CUG. 

      For example, a device with 50 actively monitored interfaces with minimal monitoring may have a higher rating that a Windows server device with full PowerShell monitoring. This is why it may seem that some collectors have more devices than others in the same CUG even after a rebalance.

      Antonio Andres

      Senior Technical Support Engineer | ScienceLogic

  • Issac's avatar
    Issac
    Contributor III

    Hi Tony,

     

     Yes , but i need a mechanism say do the rebalance every 24 hrs.

    • EricChambers's avatar
      EricChambers
      Icon for Employee rankEmployee

      Hi Issac, I'm curious, why do the collector groups need to be rebalanced daily? What problem is that solving?

      Thanks.

    • TonyAndres's avatar
      TonyAndres
      Icon for Moderator rankModerator

      Hello Isaac,

      Currently the CUG rebalance does not run on an interval, there is no functionality to enable the rebalance to occur on an interval and there are no plans to implement this as a feature in the future. 

      I recommend submitting this to the Ideas Hub as a feature request. There a product manager will review the ask and take it into consideration when implementing new features into SL1.

      Antonio Andres

      Senior Technical Support Engineer | ScienceLogic

  • Hello Isaac,

    While the collector rebalancing does not occur on an interval, there are certain situations outside of a manual run where a rebalance is triggered. This is explained further in the KB article When a Collector Load Balancing is triggered, and what impact can that have? (sciencelogic.com)

    From the article, the following can trigger a rebalance:

    1. A new device is created: the balancer assigns the device to a collector in the device's CUG.
    2. A collector fails over and enters the failed over state: the balancer assigns the failed over collector's devices to available collectors (provided the maximum allowed collector outage has not been reached).
    3. A collector fails back from the failed over state: the balancer rebalances the CUG by reassigning all devices to available collectors.
    4. The user adds or removes a collector using the UI's CUG administration page (admin_collector_groups): the balancer rebalances the CUG by reassigning all devices to available collectors (provided the maximum allowed collector outage has not been reached).
    5. The user clicks a CUG's lightning bolt in the UI's CUG administration page: the balancer reassigns all devices to the available collectors in the CUG.
    6. The user enables High Availability for a CUG in the UI's CUG administration page: the balancer reassigns all devices to the available collectors in the CUG.

    For now, there are no plans to set the collector rebalancing on an interval.

    Antonio Andres

    Senior Technical Support Engineer | ScienceLogic