SolarWinds' auto-dependency feature, while designed to reduce alert noise by suppressing downstream alerts when a parent node is down, currently fails in certain scenarios. One such case we encountered involves Cisco Viptela SD-WAN deployments.
At remote sites, the SD-WAN device should logically act as the parent node, with edge devices and connected infrastructure as children. However, SolarWinds was unable to automatically establish this relationship, resulting in alerts being triggered for child objects even when the SD-WAN parent was down.
This behavior undermines the purpose of auto-dependencies and leads to alert fatigue and false positives, especially in large-scale environments.
Also, an updated list of known auto-dependency gaps across supported vendors and device types from Solarwinds will be helpful, so that it can be taken care by manual dependency before the issue occurs.
