Disable Alerts on Active Discovery for specific instances

We have the same challenge -- what I have been told is to clone the underlying DS and effectively partition the "Applies To" across the dual DS's ala https://www.logicmonitor.com/support/datasources/creating-managing-datasources/datasource-discovery-filters/ .  On the one that needs to be limited, more filters can be added.  I do understand this concept, but I continue to be concerned this methodology will lead to the equivalent of spaghetti programming -- many clones with no relation and no way to ensure that common features are maintained across the clone group.  I proposed a "linked clone" feature a while back that would help with this via inheritance, but no idea if or when that would be implemented.

BTW -- the default interface DS does not account for ifAdminStatus.  Ports will be excluded if ifOperStatus is not up, but once it is up, it becomes an instance, and will alarm even if you later shutdown the port.  That is the sort of thing that having to fix in multiple clones can be painful and error-prone.

We have a few things in the works that may help with this.  One is the ability to auto group instances based on an instance level property, which at minimum will give you the ability to centralize the manual change.  We're also re-architecting the LogicModule backend, which will provide better history and links between datasources.  We won't stop there, but those should help alleviate the pain.