Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed monitors alert when dependent monitor succeeds after failure #786

Open
mikbro2021 opened this issue Jul 29, 2021 · 1 comment
Open
Labels

Comments

@mikbro2021
Copy link

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.

@jamesoff jamesoff added the bug label Jul 29, 2021
@jamesoff
Copy link
Owner

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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants