Understanding DA caching in a CUG
We have a situation where a single DA aligned with a root device caches data about component devices which it then uses to populate metrics for both the root and component devices. Does anyone have some more detail on what happens - at a CUG level - if the collector aligned to the root device becomes unavailable? How does another collector in the CUG know that it needs to start caching data (is that via config push?) and does the whole DCM tree need to be rebuilt but aligned with a different collector? Equally - is there any smarter way to avoid the "Device failed availability" event for the child devices which is only occurring because the cached data from the root device is not available (and not because the child devices really have an availability problem)>GQL Device linked to Collector
Hi, For trouble shoot, I want to have an overview of the devices linked to the collector where the (SNMP) device is allocated to. Pulling all the devices with attributes are working fine, also the related collector group and his group members. I am not able to find a solution to get device-to-collector. Is someone having a example GQL? Any suggestions? Thanks in advance. Alfred
