Skip to main content
Solved

Automatic CUG Addition /Removal

  • October 1, 2025
  • 5 replies
  • 0 views
I

Hi All,

It is possible to automatically remove the collectors from CUG if the cpu/memory have reached above 90 % . 

The failover of devices should work with the performance of DC load as well ,not only down.

Best answer by TonyAndres

Hello Isaac,

At the moment, the CUG load balancing does not have this capability. I recommend submitting this as a feature enhancement to the Ideas Hub here in the Nexus Community, so that our Product Management team is aware there is a desire for increased performance considerations in regard to CUG load balancing.

Antonio Andres

Principal Technical Support Engineer | ScienceLogic

    5 replies

    T
    • TonyAndres
    • October 7, 2025

    Hello Isaac,

    Currently, aligning and removing collectors from a collector group is a manual process. Removing a collector if it has CPU or memory utilization over 90% is not advisable because we do not know what the root cause of what is causing the performance load. For example, if there is a single device that is misconfigured and is causing CPU to spike above 90%, removing the collector will simply load balance this device to a different collector and then that new collector will have its CPU spike to over 90%. Not to mention the added load of redistributing those devices to the remaining collectors. 

    If you do see a collector consistently at over 90%, adding a collector generally helps with spreading the load. If that still does not work, please submit a case to ScienceLogic Support and we can investigate the root cause of the issue and provide a solution.

    Antonio Andres

    Principal Technical Support Engineer | ScienceLogic

      J

      if there was some feature that facilitated this I would suggest that it was triggered via runbook actions that can be configured and not something directly related to the CUG setup. For instance in the use case given,  if you oversubscribe a CUG and all of the collectors were running over a specific CPU utilization you would not want all of your collectors removed from the group or put into a failed state. that would create complete data loss and you would be much worse off than just having some data gaps or delayed data. Lots of use cases would need to be explored to develop this kind of feature. 

       

      Jason. 

        J

        @Issac if this is something you want in the product we should come up with some reasonable use cases and then you can write something up in depth in Ideas Hub. But this would take a long time to implement into the product and has the potential to to cause more issues than solve them in my opinion. That said, its going to be a tough sell to the product management team in charge of CUG management. 

         

        J

        Sounds like a really cool use case that Skylar Analytics should be able to handle. 

        J

        @mweathersbee since you are the PM for Analytics right now bringing this to your attention. 

        Terms & ConditionsAccessibility statement