- changed status to resolved
noalert is not working
Hi, I've tested the latest version - 5.18 and I found, the "noalert" option is not working. I started getting a lot of emails from services monitored with this option, so I've reverted to 5.17.1
Comments (5)
-
repo owner -
Yes,
noalert
is not working in 5.18. -
@tildeslash Btw, maybe you could release 5.18.1 with such important bug fixes applied? 5.18 is already two months old.
Stability releases good not just in a few days after release (like it was for 5.17 and 5.12), but even at later times (and being more frequent, especially for important bugs), because, they really signify improved stability. Major releases does not give impression of stability, because, with new features they also contain new bugs.
-
repo owner @daikon we work on a new release, it should be available within ca. 1-2 weeks
-
repo owner - changed version to 5.18.0
- Log in to comment
Fix Issue
#388: The service-local alert settings didn't override global "set alert" for the same recipient properly.→ <<cset e66e00381fc0>>