Aggregate Data Collection Method

Last updated - 08 January, 2026

The Aggregate Data collection method enables you to monitor and roll up metrics across multiple discovered instances or components into a single datapoint source within a module. Instead of collecting individual values per instance at each polling interval, aggregate collection summarizes values across instances using functions such as sum, average, min, or max—to present a unified view of performance or health.

This approach is useful when monitoring higher-level metrics, for example, total memory usage across all threads or average response time across multiple services to reduce data noise, highlight trends, and optimize collection overhead.

Requirements for Configuring a Datapoint using the Aggregate Collection Method

To configure an Aggregate Data datapoint, you must have appropriate permissions to edit or create LogicModules.

Configuring a Datapoint using the Aggregate Collection Method

1. In LogicMonitor, navigate to Modules.
2. Add a new DataSource or open an existing module to add a datapoint for Aggregate Data collection. 
   For more information, see Custom Module Creation or Modules Management in the product documentation.
3. In the Collection Method dropdown menu, select “AGGREGATE DATA”.
4. In the Collection Schedule dropdown menu, select how frequently you want the data to be collected.
5. Toggle the Enable Component Discovery switch. This enables LogicMonitor to automatically identify and synchronize service components based on the Component Key and Component Values defined in the module.

6. In the Access Groups section, add access groups as needed to control who can view or edit the module.
   For more information, see Access Groups for Modules. 
7. In the AppliesTo section, based on your requirements add any AppliesTo scripting method. This determines which resources the module applies to.
   For more information, see AppliesTo Function Scripting Overview.
8. In the Component Discovery section, do the following:
   1. In the Component Identification Property field, enter the LogicMonitor property key used to uniquely identify each component (for example, system.hostname or auto.services.component).
      This key enables LogicMonitor to dynamically match discovered components during Active Discovery.
   2. In the Components field, assign the relevant components that you want to monitor.
      You can assign a maximum of 10 components. 
      
9. In the Datapoints section, add relevant normal or complex datapoints based on your requirement. 
   For more information, see Datapoint Overview.
10. Select Save.

The datapoint is saved for the module and you can configure additional settings for the module as needed. For more information, see Custom Module Creation or Modules Management.