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
I'm having an issue where sometimes a device recovery isn't issued through the Transport method.
Possibly a race condition due to the delay we have set.
For example, I have a device that went down at around 12:00. We have a 10 minute delay configured for this rule.
At 12:11 the device came back online. The 'Down notification' was send at 12:11. The recovery notification was never issued.
We have max alerts set to 1 as well.
(meanwhile it's past 16.00 and still no recovery issued)
Output of ./validate.php
-
What was the last working version of LibreNMS?
No response
Anything in the logs that might be useful for us?
There are other reports of this occuring:
https://community.librenms.org/t/alert-rule-no-recovery-alert-with-max-alert-1/22925
https://community.librenms.org/t/missing-recoveries/23858 (mine, but no replies)
The text was updated successfully, but these errors were encountered:
The database is updated after the issueAlert() process has finished. If this issueAlert() takes a few seconds, a recovery that occurs while issueAlert() is running doesn't see the active alert in the database and thus does not send a recovery alert.
The problem
I'm having an issue where sometimes a device recovery isn't issued through the Transport method.
Possibly a race condition due to the delay we have set.
For example, I have a device that went down at around 12:00. We have a 10 minute delay configured for this rule.
At 12:11 the device came back online. The 'Down notification' was send at 12:11. The recovery notification was never issued.
We have max alerts set to 1 as well.
(meanwhile it's past 16.00 and still no recovery issued)
Output of ./validate.php
What was the last working version of LibreNMS?
No response
Anything in the logs that might be useful for us?
The text was updated successfully, but these errors were encountered: