We have some disperate use cases for parenting of network relationships between devices depending on which internal teams monitor them, it would be very useful if we could turn on/off parent/child discovery by groups or functional groups rather than having to pick out each device to turn it off on after it has automagically swept the whole system. Our alerting is driven by Netreo incident management rules sending to a log which is read by the alert presentation tool for the NOC.
EG: Core Router A has several devices (B, C & D) connected to it.
Core router A is managed by NOC 1. The child devices are managed by NOCs 2 & 3.
When Core Router A goes down it may be useful to have visibility that the outage to devices BCD is caused by the outage, however NOCs 1, 2 & 3 all need to see alarms that their devices are impacted so they can contact impacted customers etc.
It's also useful in the case that NOC1 may be responsible for the children BC&D for NOC1 to have immediate visbility of the whole impact, even though this is an increase in overall alarm noise so they can immediately see the scale of the outage rather than a single line for Core Router A being down.
It would be nice if there was a way for us to make use of the parenting rules within the system while still having the option to either disable it for certain groups, or to toggle on/off alerting for groups so incidents are still created to run actions for the child devices and their teams.
Netreo Product Area | Netreo (IM) |
PLEASE EXPOSE RELATIONSHIP DATA VIA API
This can be achieved today through the "Change" options in parenting but in large environments could be very cumbersome. Would be nice to have some other options for eliminating the relationships if required