Notification Problems
Posted: Wed Oct 04, 2017 11:26 am
Hi, I am experiencing some very odd behavior with notifications, and I can't tell if it is a bug or just something to do with my implementation. I have the following two services configured:
These are effectively doing to the same thing, however one is targeting a host group (Windows_Servers), and notifies a contact group (Group1), while the other is only targeting one host (Server 1) and notifying one user. (User1) The host "SERVER1" is also in the host group "Windows_Servers".
What I am finding is that when the host has a CPU spike that would trigger both of these checks, it notifies everybody. That is the, Group1 and User1 both receive the alerts for CPU and CPU-2.
Is this some sort of limitation of having the same check command on a host twice, or should I be able to keep things separate?
In another strange incident, I just had the check go to critical and send alerts to Group1 every minute until it was resolved, despite the command clearing having notification_interval set to 0.
Thanks for any help, I have tried everything I can to make this as simple as possible and it still doesn't seem to do what I expect it to!
Code: Select all
define service{
hostgroup_name Windows_Servers
service_description CPU
_SERVICE_ID 47
is_volatile 1
check_command check_cpu!2c!public!90!80
max_check_attempts 3
normal_check_interval 1
retry_check_interval 1
check_period 24x7
notification_interval 0
notification_period 24x7
notification_options w,c,r
notifications_enabled 1
contact_groups Group1
}
define service{
host_name SERVER1
service_description CPU-2
_SERVICE_ID 108
check_command check_cpu!2c!public!90!80
max_check_attempts 3
normal_check_interval 1
retry_check_interval 1
check_period 24x7
notification_interval 0
first_notification_delay 0
notification_period 24x7
notification_options w,c,r
notifications_enabled 1
contacts User1
}What I am finding is that when the host has a CPU spike that would trigger both of these checks, it notifies everybody. That is the, Group1 and User1 both receive the alerts for CPU and CPU-2.
Is this some sort of limitation of having the same check command on a host twice, or should I be able to keep things separate?
In another strange incident, I just had the check go to critical and send alerts to Group1 every minute until it was resolved, despite the command clearing having notification_interval set to 0.
Thanks for any help, I have tried everything I can to make this as simple as possible and it still doesn't seem to do what I expect it to!