Optimization of Dependent Alert Mapping
Last updated - 26 September, 2025
To monitor a large number of resources in Dependent Alert Mapping (DAM), you can increase the DAM node limit beyond the default 10,000 nodes. To increase the DAM node limit, establish connections between entry point seeds and their associated Collectors. These connections are created automatically through Topology and ERI sources.
When connected, a Collector can be used as the entry point in the DAM rule. This setup enables you to further scale the node limit. To do so, contact your system administrator and configure the Collector and resource settings. This ensures that scaling occurs without downtime, topology service timeouts, or disruption to the existing DAM functionality.
Requirements for Optimizing Dependent Alert Mapping
To optimize Dependent Alert Mapping, you need the following:
- A dynamic resource group that pulls in all resources defined as entry points in DAM rules. You can filter resources by a common characteristic (type, role, or tag) or assign a custom property to keep them consistently grouped.
- Download the following JSON files on your machine:
Optimizing Dependent Alert Mapping
To optimize DAM, complete the following steps:
- Add PropertySource to Assign ERIs to Collectors
- Add TopologySource to Connect Entry Point Seeds and Collectors
- Create Collector Group for Dependent Alert Mapping
- Modify Dependent Alert Mapping Rule
- Verify Dependent Alert Mapping
Adding PropertySource to Assign ERIs to Collectors
- In LogicMonitor, navigate to Settings > LogicModules.
- On the My Module Toolbox page, select
Add.
- In the Add window, select Import from File.
- Browse for addERI_collectorMapping.json and import the file.
After the module imports successfully, the Modules page displays. - Select the AppliesTo tab.
By default,system.collector
is set totrue
. - Select
Test AppliesTo to view the resources connected to the Collector.
The resources display in the side panel. - Select Cancel to close the PropertySource.
The new ERI applies to the Collector device with the formatlmcid_collectorid
.
You can view the ERI in thepredef.externalResourceID
property.
For example,predef.externalResourceID
=lmcid_100
where,collectorid=100
.
Adding TopologySource to Connect Entry Point Seeds and Collectors
- In LogicMonitor, navigate to Settings > LogicModules.
- On the My Module Toolbox page, select
Add.
- In the Add window, select Import from File.
- Browse for collector_to_entrypoint_toposource.json and import the file.
- Select Save.
After the module imports successfully, the TopologySource Modules page displays. - Select the AppliesTo tab.
- Enter
join(system.groups,",") =~ "Entry point resource group"
. - Select
Test AppliesTo to view the resources connected to the Collector.
- Select Save.
This automatically creates edges (connections) between entry point devices and the Collectors monitoring them.
Creating Collector Group for Dependent Alert Mapping
- In LogicMonitor, navigate to Resource Tree >
> Dynamic Group.
For more information, see Dynamic Resource Groups. - Create a new dynamic resource group.
For example,DAM_Entry_Point_Collectors
. - Add all Collectors to this group.
For example, Collector1, Collector2, and Collector3.
The group acts as the entry point in DAM.
Modifying Dependent Alert Mapping Rule
- In LogicMonitor, navigate to Settings > Alert > Dependent Alert Mapping.
- On the Dependent Alert Mapping page, select
Manage.
- Select “DAM_Entry_Point_Collectors” in the Group field and “*” in the Resources field.
Alerts from entry point devices depend on the Collector group. - Verify the entry point settings.
For more information, see Configuring Dependent Alert Mapping. - Select Save.
Verifying Dependent Alert Mapping
- In LogicMonitor, navigate to Settings > Audit Logs.
The Audit Logs page displays. - Verify the logs to confirm DAM mappings are applied correctly.