Alert is re-sent after monit reload
Issue #359
new
I had upgraded from monit 5.16 to monit 5.17.1 when an alert (swap usage) was sent per E-Mail. Then I changed just a comment in monitrc and used "monit reload" (just to try it). The monit sent another swap usage alert. In my understanding an alert should not be resent as long as the trigger condition persists (and it is configured that way).
Comments (3)
-
repo owner
-
repo owner
-
assigned issue to
Tildeslash
- marked as major
- marked as enhancement
-
assigned issue to
-
repo owner
Issue
#635was marked as a duplicate of this issue. - Log in to comment
Currently the service error state is not persistent across monit restart/reload. We will make it persistent, save and restore the state:
1) if the error persists after monit restart, no alert duplicate will be sent
2) if the service had error which disappeared after monit restart, a "success" alert will be sent (currently in such case monit won't notify about the service recovery)