Notification not being sent event if status="on", looks like notifd is not using the status in the config file properly

Description

Notifd never send notification even if I go under Home / Admin / Configure Notifications / Event Notifications and I turn Event Notifications to ON (yes, Notifications Status is turned ON under admin)

This worked properly a few snapshots ago but it now fails.

Here's what I have for instance under notifd.log even though my event notification is turned on for this particular event.

2011-07-29 00:36:59,909 DEBUG [Notifd:BroadcastEventProcessor] NotificationFactory: Event uei.opennms.org/vendor/cisco/traps/SNMP_Link_Down is configured to supress notifications.

Changing it to OFF or ON doesn't change the message, it is always the same. I checked the notifications.xml file and the status changes to what I set it in the web interface so the config file seems okay, it just looks like notifd is not using/reading it properly.

Notifications is probably the most important part of our OpenNMS usage so this is critical that it works for us.

Thanks

Patrick Monfette

Environment

Linux, CentOS 5 64 bits

Acceptance / Success Criteria

None

is duplicated by

Lucidchart Diagrams

Activity

Show:

Andy Ellsworth September 6, 2011 at 1:18 PM

Confirmed fixed in my environment (1.9.91, 2011-09-03 snapshot).

Alejandro Galue August 26, 2011 at 1:16 PM

Fixed on revision a1500a41ac2ae2a8563f20c20c9f0cd1767cf038 for 1.10.

Now the default value for 'notify' will be 'true' (as it was before), so if it doesn't exist on event definition will be treated as true; but if you specify it, the provided value will be used.

sandeep August 24, 2011 at 4:27 PM

I'm having the same issue even after setting notify='true'

Andy Ellsworth August 19, 2011 at 2:39 PM

I'm having the exact same problem on the 8/17 snapshot. Notifications don't work, same message in DEBUG logs.

Alexander Kolov August 18, 2011 at 10:48 AM

I was able to get notifications sent by editing eventconf.xml and adding attribute notify='true' for logmsg nodes for specific events. For example:

<event>
<uei>uei.opennms.org/nodes/nodeLostService</uei>
<event-label>OpenNMS-defined node event: nodeLostService</event-label>
<descr>
&lt;p&gt;A %service% outage was identified on interface
%interface%.&lt;/p&gt; &lt;p&gt;A new Outage record has been
created and service level availability calculations will be
impacted until this outage is resolved.&lt;/p&gt;
</descr>
<logmsg dest='logndisplay' notify='true'>
%service% outage identified on interface %interface% with reason code: %parm[eventReason]%.
</logmsg>
<severity>Minor</severity>
<alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%interface%:%service%" alarm-type="1" auto-clean="false" />
</event>

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created July 29, 2011 at 12:40 AM
Updated January 27, 2017 at 4:20 PM
Resolved August 26, 2011 at 1:16 PM