Possible Conflict with MIB Compiler

[Mike Kelly]

It seems that however the PagerDuty plugin integrates with event config means that, every time you generate a new events/*.xml file via the MIB Compiler, you get these entries added to eventconf.xml:

   <event>
      <uei>uei.opennms.org/pagerduty/sendEventSuccessful</uei>
      <priority>0</priority>
      <event-label>PagerDuty: Successfully sent event</event-label>
      <descr>Successfully sent event via REST API for alarm with reduction key: %parm[reductionKey]%</descr>
      <logmsg dest="logndisplay">PD: Successfully sent event for alarm: %parm[reductionKey]%</logmsg>
      <severity>Normal</severity>
      <alarm-data reduction-key="%uei%:%parm[routingKey]%:%parm[reductionKey]%" alarm-type="2" clear-key="uei.opennms.org/pagerduty/sendEventFailed:%parm[routingKey]%:%parm[reductionKey]%" auto-clean="false"/>
   </event>
   <event>
      <uei>uei.opennms.org/pagerduty/sendEventFailed</uei>
      <priority>0</priority>
      <event-label>PagerDuty: Failed to forward event to PagerDuty</event-label>
      <descr>Failed to sent event via REST API for alarm with reduction key: %parm[reductionKey]%. Message is: %parm[message]%</descr>
      <logmsg dest="logndisplay">PD: Failed to sent event for alarm: %parm[reductionKey]%</logmsg>
      <severity>Critical</severity>
      <alarm-data reduction-key="%uei%:%parm[routingKey]%:%parm[reductionKey]%" alarm-type="1" auto-clean="false"/>
   </event>