Hi Kevin,
You have to create a notification or modify an existing one in the Icinga director. After deploying the config, there should be an entry in the “Benachrichtungen” section of the host/service.
For example (running on my Vagrant Icinga standalone box):
Sample config
apply Notification "test-notification-1" to Host {
import "my-notification-template"
assign where match("*", host.name)
}
Do you have a notifications.conf file? Depending on your setup, there might be a conf.d directory. Mine is /etc/icinga2/conf.d/, so any .conf file residing in this directory is included in the configuration (include_recursive "conf.d" in the icinga2.conf file).
Notifications should stay in a file named notifications.conf, so you’ll find the definitions very easy in the future.
Hi, all right, you’re using the Icinga director. Sorry, I’ve missed that part.
Please undo your changes in the conf files. Since you’re using the director, the notifications have to be defined in the director too. You’ll find the notification and notification templates in the director menu.
The error message is truncated in your screenshot.
But in the previous screenshot you’ve added Critical, … in the notification for a host object. Host objects can only be in the states Up and Down. So you have to specify Up and Down only. After changing this, try to deploy the config again.
Hi,
ideally you would create a service template having “Send notification = yes”, and reference that in your apt service in the Imports field.
Sorry for the late response, I was a while off…
With all due repsect, have you thought about attending a course about Icinga and the Icinga Director? I think that would be great to settle the fundamentals.