[prev in list] [next in list] [prev in thread] [next in thread]
List: opennms-buglist
Subject: [Buglist] [Bug 3998] New: A lot of OpenNMS defined events do not include nodelabel in description
From: bugzilla () opennms ! org (bugzilla at opennms ! org)
Date: 2010-07-30 7:55:34
Message-ID: bug-3998-627 () http ! bugzilla ! opennms ! org/
[Download RAW message or body]
http://bugzilla.opennms.org/show_bug.cgi?id=3998
Summary: A lot of OpenNMS defined events do not include nodelabel
in description
Product: OpenNMS
Version: 1.8.1
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P1
Component: Events/Traps
AssignedTo: buglist at opennms.org
ReportedBy: dk at in-telegence.net
Let's take the nodeDown event as an example:
<event>
<uei>uei.opennms.org/nodes/nodeDown</uei>
<event-label>OpenNMS-defined node event: nodeDown</event-label>
<descr>
<p>All interfaces on node %parm[nodelabel]% are
down.</p> <p>This event is generated when node
outage processing determines that all interfaces on the node
are down.</p> <p>New outage records have been
created and service level availability calculations will be
impacted until this outage is resolved.</p>
</descr>
<logmsg dest='logndisplay'>
Node %parm[nodelabel]% is down. %parm[eventReason]%
</logmsg>
<severity>Major</severity>
<alarm-data reduction-key="%uei%:%dpname%:%nodeid%" alarm-type="1"
auto-clean="false" />
</event>
Since nodelabel is not a parameter, it should read %nodelabel% instead of
%parm[nodelabel]%.
There are several other events in eventconf.xml where %parm[nodelabel]% is used
as well.
--
Configure bugmail: http://bugzilla.opennms.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic