Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #10225] Host notification type is PROBLEM but should be RECOVERY #3439
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10225
Created by mwaldmueller on 2015-09-28 07:46:44 +00:00
When a host or service recovers from a warning/critical state the notification.type should be RECOVERY. Instead of the notification type has the value PROBLEM.
Here's an output of a default email notification with the subject: "PROBLEM - testhost is UP"
2016-03-10 13:32:57 +00:00 by mfriedrich c0e175d
2016-03-11 08:29:07 +00:00 by mfriedrich 5b6a6f8
2016-03-11 14:58:13 +00:00 by mfriedrich ee7af88
2016-03-15 08:47:59 +00:00 by mfriedrich 3bd6848
2016-03-15 12:11:01 +00:00 by mfriedrich f386920
Updated by mfriedrich on 2016-02-24 23:02:25 +00:00
Service exit states 0 and 1 (OK and Warning) are treated as Up, while 2 (Critical) is equivalent to Down. I believe that somewhere when triggering notifications, it is not taken into account that the notification type is NotificationProblem but not NotificationRecovery.
recovery needs to be adjusted for host checks.
Updated by mfriedrich on 2016-03-10 13:33:25 +00:00
The problem is that you cannot simply pass the state WARNING to a host check result. Using a dummy check which is executed on-demand solves the simulation issue.
Steps to reproduce:
Requires more tests.