Page 2 of 2
Re: SNMP Traps best practices
Posted: Mon Jun 17, 2013 4:51 pm
by BanditBBS
sreinhardt wrote:You generally have a good handle on whats going on around here, so I'm just going to throw this out there on the off chance it was overlooked. While your service has notify for everything, does your contact also? Could be that its just getting restricted there.. but again I would think you covered that already.
That is what I meant by my account. However, that was just checking my XI account. I will check the actual contact configuration file when I get in the office tomorrow. However, I know I get recovery messages because if I submit a passive result and set it critical, I get that alert and then if I submit another passive result set to OK, I get the recovery. If I then send another passive result set to OK I do not get any alert.
Re: SNMP Traps best practices
Posted: Mon Jun 17, 2013 4:57 pm
by sreinhardt
if I submit another passive result set to OK, I get the recovery. If I then send another passive result set to OK I do not get any alert.
OK, so you do get the initial recovery email, just not a second or more notification. Also, I thought you might have been referring to that before, just wanted to be sure.
Re: SNMP Traps best practices
Posted: Tue Jun 18, 2013 7:42 am
by BanditBBS
sreinhardt wrote: if I submit another passive result set to OK, I get the recovery. If I then send another passive result set to OK I do not get any alert.
OK, so you do get the initial recovery email, just not a second or more notification.
Correct, which means my contact is fine., but just to show you:
Code: Select all
define contact {
contact_name clarkj
alias Jim Clark
host_notification_period clarkj_notification_times
service_notification_period clarkj_notification_times
host_notification_options d,u,r,f,
service_notification_options w,u,c,r,f,
email [email protected]
pager 7402782037
host_notifications_enabled 1
service_notifications_enabled 1
use xi_contact_generic
}
It is looking like I have to change all traps for these devices to critical if I want alerted on them all, unless there are any other hints to try. technically, it won't be hard, I can just add a section into snmptraphandling.py that says if host=whatever then severity=critical. I'd just rather not have to adjust that script more than I already have
Re: SNMP Traps best practices
Posted: Tue Jun 18, 2013 1:10 pm
by abrist
BanditBBS wrote:It is looking like I have to change all traps for these devices to critical if I want alerted on them all
Unfortunately, this seems to be the case.