Dynamic Device Groups - constrain membership to parent folder | Product Discussions

ldoodle · 2024-02-07T08:11:03Z

Hi,We have the following hierarchy setup:Our company is top level, e.g. LOGICMONITOR|--Customer Name, e.g. GOOGLE, MICROSOFT|----’All Devices’ static group (when we add new devices, we add them here)|----Category named group, e.g. ‘Infrastructure’ static group (with no actual devices added here)|------Function named group, e.g. ‘Active Directory’, ‘DNS Server’, etc. dynamic group with custom query (hasCategory("MicrosoftDomainController"), hasCategory("Windows_DNS") etc.)So:LOGICMONITOR|--GOOGLE|----All Devices|------DEVICE1 (pretend this is an AD server)|------DEVICE2 (pretend this is an AD server)|----Infrastructure|------Active Directory|--------DEVICE1 (correct)|--------DEVICE2 (correct)|--------DEVICE3 (incorrect)|--------DEVICE4 (incorrect)|------DNS Server|--MICROSOFT|----All Devices|------DEVICE3 (pretend this is an AD server)|------DEVICE4 (pretend this is an AD server)|----Infrastructure|------Active Directory|--------DEVICE1 (incorrect)|--------DEVICE2 (incorrect)|--------DEVICE3 (correct)|--------DEVICE4 (correct)|------DNS Server The problem with this, and it is partly a misunderstanding on my part, is that I expected the (nested) dynamic groups to automatically be constrained to their parent container.How do I achieve this? The only thing I can think of is having the function-named group custom query be something like this:join(system.groups,",")=~"GOOGLE/_All Devices" && hasCategory("MicrosoftDomainController")But that means every dynamic group for every customer will need that, which is fine. But, is there a better, more native/default way?Thanks

MoreDiscussions

Dynamic Device Groups - constrain membership to parent folder | Product Discussions | LogicMonitor Community