You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we have a device (#1) that fails and then a device (#2) that #1 depends on fails and recovers, we get an alert for the dependent device (#1).
To explain more fully, an AP is hanging off a switch. The AP monitor 'depends' on the the switch.
The AP fails and we get an correctly alert. The switch then fails and we correctly get an alert for the switch. The switch recovers and we incorrectly get an alert for the AP. The system should 'remember' that the AP was down before the switch went down/up.
The text was updated successfully, but these errors were encountered:
Ah yeah I think I see why this is happening... nonw I need to figure out the best way to fix it :)
(I think it's because "skipped" monitors, those with failed dependencies, internally pretend to have succeeded, so when the switch fails, the AP monitor is marked as suceeded, which means when the switch is up again, the AP monitor failure is seen as new.)
If we have a device (#1) that fails and then a device (#2) that #1 depends on fails and recovers, we get an alert for the dependent device (#1).
To explain more fully, an AP is hanging off a switch. The AP monitor 'depends' on the the switch.
The AP fails and we get an correctly alert. The switch then fails and we correctly get an alert for the switch. The switch recovers and we incorrectly get an alert for the AP. The system should 'remember' that the AP was down before the switch went down/up.
The text was updated successfully, but these errors were encountered: