The current method of building dependencies is EXTREMELY inefficient and not at all user friendly. We just migrated away from WhatsUp Gold to Solarwinds and this is one area that Solarwinds simply got wrong. Solarwinds is much better that WhatsUp Gold in most aspects, but not this one. Building dependencies in Solarwinds simply sucks!
I have 3 major issues here:
1. Auto dependencies simply don't work.
2. Using groups is the most efficient way to build dependencies, but I have organized all of my sites into groups, as I assume most users would that have to manage multiple sites. You cannot use these groups for your dependencies because you would have to leave out the primary router at each site because the parent cannot be in the same group as the "child" group. Users would have to create separate groups just for dependencies, but then these groups would show up in all your dashboards, making for more clutter and more confusion when viewing dashboards, especially for helpdesk level personnel.
3. Having to build manual dependencies per child is simply idiotic. If we could build dependencies per parent and select multiple children, this would be WAY more efficient and actually makes WAY more sense in how dependencies actually work. For example, most organizations would have one primary router at a site with a bunch of switches, servers, access points, firewalls, etc behind this router. If this one router is offline then all other devices at the site would be unreachable. Why can't we build a dependency selecting the one parent and then select all children under this parent?
