Hi
I meant the history tab in at the host object. if the host or service is in a non ok state you should see if the notification rule is working:
e.g.
here is no notification sent, because nobody in our company wants to have “unkown”-messages.
In the last time there were some threads with a similar problems. Maybe they could help:
- Notification by mail
- Need to setup Icinga2/Icingaweb2 to send email alerts only for ping service
- Strange behaviour of notifications
If you can send a forced notification via icingaweb2 it couldn’t be something like SELinux or wrong file permisisons. the same if you can send messages via the bash. I think something is wrong with the apply rule. In the first link is a way how to check if the rules are applied