Adding Collector Group

Last updated on 26 April, 2024

Grouping your collectors into logical units can streamline account management, simplify end user permission settings, improve efficiency, and more. LogicMonitor supports two types of collector groups:

  • Standard collector groups
  • Auto-balanced collector groups (ABCG)

Standard Collector Groups

Standard collector groups primarily assist with collector organization. For example, you can to organize collectors into groups based on any of the following shared characteristics:

  • Physical location – If you have infrastructure across multiple data centers or offices, grouping collectors based on their locations can simplify assigning collectors throughout your account (e.g. when devices are added).
  • Customer – If you’re an MSP, grouping collectors by customer can make it easier to quickly find a particular collector, and additionally simplifies the collectors page display when you have a large number of collectors in your account.
  • Environment – You may want to group collectors based on whether they are in a development, QA, production, or other environment. This will enable you to set user role permissions per group, to ensure that your team members have the appropriate access.

Auto-balanced Collector Groups

Auto-Balanced Collector Groups (ABCGs) provide functionality beyond organization. The collectors in an ABCG share device load, allowing for dynamic device balancing, scaling, and failover.

Adding Collector Group

  1. Navigate to Settings > Collectors.
  2. Under the Collectors tab, select the Add Collector Options dropdown.
  3. Select Add Collector Group.
  4. Toggle the Auto Balanced Collector Group option to enable auto balancing for the collector group. Auto-balancing allows you to share device load among a group of collectors.
  5. Enter a name and description of your new collector group.
  6. Define the key and value pair to add properties on your collector that can then be tokenized in collector-related alert messages. This is particularly useful for routing collector down, failover, and failback alerts through an external ticketing system.
    For example, your team in Austin is responsible for a specific subset of collectors. To ensure the Austin team is properly notified in the event one of their collectors goes down, you can assign these collectors a custom property. Once assigned, the property can be tokenized (##team##), and used to route alerts to the proper team via your organization’s ticketing system. The token is substituted with the property value at the time of generation so that the alert or integration delivery can include dynamic information.
  7. If you designated your new group as an Auto-Balanced Collector Group, the Rebalance Threshold – Instance Count option is displayed. You can adjust the threshold instance count.

Moving a Collector to Collector Group

Collectors are assigned to collector groups at the time collectors are added. As your LogicMonitor deployment evolves over time, it is likely you’ll want to move collectors among groups to suit new organizational needs, create auto-balanced groups, and so on. To move collectors from one collector group to another, navigate to Settings > Collectors. From the Collectors page, either:

  • To move collectors in bulk – Select the checkbox on the table header to select all the collectors and select Actions > Move selected items to Group and then confirm your action.
  • To move a single collector – Select the Manage icon of the collector you want to move and then select a new group in the Collector Group field.

Moving Collectors Between Standard and ABCG

Collectors function very differently depending upon whether they are members of a standard collector group or an Auto-Balanced Collector Group (ABCG). Collectors in a standard group operate independently of one another and each manually designates a static failover collector. Collectors in an ABCG dynamically fail over to other collectors in the ABCG, thus requiring no manually designated failover collector. This becomes an important distinction when moving collectors between these two collector group types. You must consider the following points:

  • Moving from standard collector group to ABCG. When moving a collector out of a standard collector group to an ABCG, note the following:
    • The collector’s Failover Collector designation will be discarded. ABCGs employ a dynamic rebalancing algorithm upon collector failover; they don’t rely upon a one-to-one manual failover designations between collectors.
    • There are several characteristics collectors belonging to the same ABCG must share.
    • You decide whether the devices currently monitored by the collector should be immediately enabled for auto balancing. Upon moving, you’ll be presented with the Do not auto balance monitored devices option. This option, when selected, leaves the devices assigned to their current collector, allowing you to manually enable the devices on a case-by-case basis for participation in auto balancing.
  • Moving from ABCG to standard collector group. When moving a collector out of an ABCG to a standard collector group, it’s important to remember that the collector has no failover designation. You’ll need to open its settings and assign one from the Failover Collector field.

Managing Collector Groups

You can edit or delete collector groups from the collectors page.

  1. On the Collectors page, select the collector group that you want to edit or delete.
  2. Select the Manage icon.

    The Manage Collector Group page is displayed.

    After updating, save the changes.
    To delete the collector group, select Delete.

Note: Note: A combination of collector group and device permissions impact how individual users can interact with collectors within the account.

In This Article