Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-8651

pathOutage event's reduction key should allow reducing on single critical path

    XMLWordPrintable

    Details

      Description

      The current event defintion for event uei.opennms.org/nodes/pathOutage doesn't allow to reduce the events on a single critical path:

        <event>
          <uei>uei.opennms.org/nodes/pathOutage</uei>
          <event-label>OpenNMS-defined node event: pathOutage</event-label>
          <descr>
                              &lt;p&gt;The state of node %parm[nodelabel]% is unknown
                              because the critical path to the node is down.&lt;/p&gt;
                              &lt;p&gt;This event is generated when node outage processing
                              determines that the critical path IP address/service for
                              this node is not responding..&lt;/p&gt;
                      </descr>
          <logmsg dest="logndisplay">
                              %parm[nodelabel]% path outage. Critical path =
                              %parm[criticalPathIp]% %parm[criticalPathServiceName]%
                      </logmsg>
          <severity>Major</severity>
          <alarm-data reduction-key="%uei%:%dpname%:%nodeid%" alarm-type="3" auto-clean="false"/>
        </event>
      

      That means, if a critical path is down, users will show an alarm for every nodes behind this critical path.

      Also, there's no corresponding clear event, so users will have to clear all these alarms manualy.

      Changing the reduction key to the following would allow event reduction on a single path outage:

          <alarm-data reduction-key="%uei%:%parm[criticalPathIp]%:%parm[criticalPathServiceName]%" alarm-type="3" auto-clean="false"/>
      

        Attachments

          Activity

            People

            Assignee:
            stcyr Cyrille Bollu
            Reporter:
            stcyr Cyrille Bollu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: