Forum Discussion
Hello Teppo,
In the System > Manage > Dynamic Applications page, if you click on the wrench icon for the dynamic app you want modified, you can change the Collector Affinity in the Properties tab. You have the following 3 choices:
- Default. If the Dynamic Application is automatically aligned to a component device during discovery, then the Data Collector assigned to the root device will collect data for the Dynamic Application. Otherwise, the Data Collector assigned to the device running the Dynamic Application will collect data for the Dynamic Application.
- Root Device Collector. The Data Collector assigned to the root device will collect data for the Dynamic Application. This guarantees that a group of collection jobs that cannot be split up run on a single Data Collector. You might select this option if this Dynamic Application has a cache dependency with one or more other Dynamic Applications, if you are unable to collect data for devices and Dynamic Applications within the same Device Component Map on multiple Data Collectors in a collector group, or if the Dynamic Application will consume cache produced by a Dynamic Application aligned to a non-root device (for instance, a cluster device).
- Assigned Collector. The Data Collector assigned to the device running the Dynamic Application will collect data for the Dynamic Application. This allows Dynamic Applications that are automatically aligned to component devices during discovery to run on multiple Data Collectors. You might select this option if this Dynamic Application has no cache dependencies with any other Dynamic Applications, if you want the Dynamic Application to be able to make parallel data requests across multiple Data Collectors in a collector group, or if the Dynamic Application can be aligned using mechanisms other than auto-alignment during discovery (for instance, manual alignment or alignment via Device Class Templates or Run Book Actions).
For the example you provided above, you may want to set the affinity to Assigned Collector so that the dynamic app will always be aligned to the same collector as the device itself. Setting it on the dynamic app level will always select this affinity when SL1 aligns this specific app.
Antonio Andres
Principal Technical Support Engineer | ScienceLogic
Hi Antonio,
well, my issue has been with devices that are merged from two devices which are in separate CUGs. And when you align DA to device then SL1 makes the decision to which CUG it puts it. And whatever I try it always goes to wrong CUG. So when merged device is:
- device1 (snmp monitored, in CUG1)
- device2 (API monitored, in CUG2)
then always the snmp DA I try to align there goes to CUG2, obviously SL1 thinks that the device with bigger DID is the default, and this case also root, and of course the one that does not have snmp access to that network.
Teppo Tähkäpää