I searched around a bit for this question, so I hope this isn't a duplicate:
Characters:
Node 1 - Primary Internet Connection
Node 2 - Secondary Internet Connection
Stage:
Dozens of remote locations with this exact setup.
Scenario:
We were raised the question of automating some reminders to be sent out to certain people if were to fail over from Node 1 to Node 2; specifically that a resource will be made unavailable until Node 1 becomes the primary again. Me being the savvy SolarWinds administrator (best one this company has, and not just because I'm its only admin
), I suggested we use SolarWinds; parent/child relationship, should be no problem, right?
I've severly over-estimated my capability as a SolarWinds admin it seems.
In setting up the alert, I did the following:

But this failed to do what I thought it would. In digging around, I believe Child Status does not, in fact, refer to the node's child, but rather to sub-resources of said node. That's as far as I understand it, anyway, I could be wrong. So - Is this possible? I'm probably just going to automate this in a batch script with some pings, or maybe there are other tools that people are using that makes this a moot point, but it got me curious. I know that doing parent/child relationships can suppress alerts the child would otherwise trigger should the parent die, but is that the extent of the parent/child relationship in SolarWinds?
Thank you much for reading, I'll try to get back to comments as quickly as I can.