problem with notifications and contact core . not trigged

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: problem with notifications and contact core . not trigge

Post by hsmith »

Have you tried making XI users for the contacts that are not receiving emails?
Former Nagios Employee.
me.
psteam
Posts: 32
Joined: Fri Dec 02, 2011 12:03 pm
Location: Montreal, Quebec

Re: problem with notifications and contact core . not trigge

Post by psteam »

yes i have done it again
the contact is called contact1 and you can see on the screenshot its triggered and i received the email

i think my workaround will be to create xi users.
You do not have the required permissions to view the files attached to this post.
Mediagrif
Prod Support Team
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: problem with notifications and contact core . not trigge

Post by lmiltchev »

Creating "xi users" as monitoring contacts is straight forward, and it can save you lots of headaches. However, I don't believe this is your problem... You have:
define contact {
contact_name testcontact1
alias testcontact1
host_notification_period xi_timeperiod_24x7
service_notification_period xi_timeperiod_24x7
host_notification_options d,u,r,f,s,n,
service_notification_options w,u,c,r,f,s,n,
email [email protected]
use xi_contact_generic
}
Did you notice the "n" option? When you have "n" selected, notifications won't be sent.
Contact - host notification options

This directive is used to define the host states for which notifications can be sent out to this contact. Valid options are a combination of one or more of the following:
d = notify on DOWN host states,
u = notify on UNREACHABLE host states,
r = notify on host recoveries (UP states),
f = notify when the host starts and stops flapping, and
s = send notifications when host or service scheduled downtime starts and ends.
If you specify n (none) as an option, the contact will not receive any type of host notifications.

Parameter name: host_notification_options
Required: yes
Contact - service notification options

This directive is used to define the service states for which notifications can be sent out to this contact. Valid options are a combination of one or more of the following:
w = notify on WARNING service states,
u = notify on UNKNOWN service states,
c = notify on CRITICAL service states,
r = notify on service recoveries (OK states), and
f = notify when the host starts and stops flapping, and
s = send notifications when host or service scheduled downtime starts and ends.
If you specify n (none) as an option, the contact will not receive any type of host notifications.

Parameter name: service_notification_options
Required: yes
Be sure to check out our Knowledgebase for helpful articles and solutions!
psteam
Posts: 32
Joined: Fri Dec 02, 2011 12:03 pm
Location: Montreal, Quebec

Re: problem with notifications and contact core . not trigge

Post by psteam »

thats it the N
sometimes the most obvious options is the one that slips by
thank you
resolved!
Mediagrif
Prod Support Team
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: problem with notifications and contact core . not trigge

Post by rkennedy »

Glad to see this fixed. We'll go ahead and close this out now. If you ever need assistance in the future, feel free to open a new thread!
Former Nagios Employee
Locked