Allow Dependencies Within Groups

I might have missed it in the archive of wonderful ideas that is thwack but will it ever be possible to have dependencies within the same group of nodes? Currently we maintain a group of nodes to include the WAN carrier, boundary topology, and local LAN and I'm repeatedly asked to try and tier the application data to maximize visibility of the down node (say the WAN device) and not have the entire location show down/down (the operations guys lose their mind when they see all that red).

Find more posts tagged with

dependencies

npm

Status: None

Comments

adatole

If I understand what you want, I think you have the relationship wrong. Groups are used IN dependencies, not the other way around.

So let's say you have a router connected to 2 load-balanced switches, which is connected to 10 servers. Ignoring - for the moment - SolarWinds ability to automatically determine topology, you would create

1) a group for the switches

2) a group for the servers which is a query for everything in that subnet that is NOT the switches or the router.

THEN you create 2 dependencies:

1) the switch group is the child of the router

2) the "everything in the site" group is the child of the switches.

Finally, to allow groups to use dependencies would likely create a circular relationship in what is already an over- (and often mis-) used feature (namely groups). Most of the time what you want to accomplish with groups can be done with custom properties in a much more efficient way, in terms of SolarWinds processing.

emtox

Almost - if the groupings were broken out like that it'd be easier no doubt and logically the solution you provided would make sense. The lines start to blur once you add in four managing authorities (some of who play nice with our polling, others who don't for various political/sandbox reasons which) - I'd have to break out each group we currently have into several and then link them (not ideal, but possible given a large enough stretch of free time anything is possible).