I am also looking for similar situation in my network.
If parent device went down, then all the devices connected to it will showed up as unreachable. With that my mailbox got full of emails.
So is there any way out for it. What I want is if particular device went down and the devices which went unreachable should come in a Single Email ?
Above all I do not want my general monitoring to get disturbed. If particular device went then there should be email for it in my mailbox.
Very thanks for your response.
I had gone through that link. But that specified information we had already implemented.
Let me clear my scenario more briefly.
Let us suppose if parent went down .. for example Firewall. In that case what will happen, we will get bunch of emails showing that firewall is down, and other alerts will speak of devices went unreachable. The emails will be as many as the child notes went unreachable.
Can I get a way out of these bunch of emails. Instead of getting alerts separately, can that be classified in single email, mentioning device is down and these child notes become unreachable. Thats all. Dependencies and groups are already built off.
In the dependencies, what you want is (per your example):
Firewall (parent dependency) -> child dependency group
What this means is that as soon as the firewall is shown as down any nodes in the group will then be unmanaged, which will suppress alerts. If some nodes are unresponsive before the firewall you may get an alert from it but it's fairly unlikely.
Were these alerts will be completely suppressed . So the procedure to edit these decencies will be same right.. the steps and all.
Any words, before I raise the change ?
[Note: If you want to define a dependency so that the reported states of child objects are dependent on the status of multiple parent objects, create a group including all parent objects, and then select it on this view. For more information, see “Creating Groups” in the SolarWinds Orion Common Components Administrator Guide.] that i dont need.
That is correct. You're doing the right thing.
If you want a group of objects to be dependent on the parent, then you need to have or create that group. If you want it to be a single object, define accordingly.
rob.hock's link is spot on and should help here. You'll need to go to $servername/Orion/Admin/DependenciesView.aspx
To highlight some really basic concepts of what happens, you can: assign a node, interface or group to be the parent dependency and do likewise for the child which is dependent on the parent. So you can stack dependencies however is necessary, to account for redundancy as applicable.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.