anchor.diff:        <severity>Minor</severity>
         <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%interface%:%service%" alarm-type="1" auto-clean="false"/>
      </event>
  -```
  +----
   
   Every event definition has this same basic structure.
   See <<ga-events-anatomy-of-an-event,Anatomy of an Event>> for a discussion of the structural elements.
  
positive.code: Each *tributary file* contains a top-level `<events>` element with one or more `<event>` child elements.
  Consider the following event definition:
  
  ```xml
     <event>
        <uei>uei.opennms.org/nodes/nodeLostService</uei>
        <event-label>OpenNMS-defined node event: nodeLostService</event-label>
  
negative.code: 
  After making manual changes to `OPENNMS_HOME/etc/eventconf.xml` or any of its tributary files, you can trigger a reload of the event configuration by issuing the following command on the {opennms-product-name} server:
  
  [source,sh]
  ----
  OPENNMS_HOME/bin/send-event.pl uei.opennms.org/internal/reloadDaemonConfig -p 'daemonName Eventd'
  ----
  
  === Debugging
  
  When debugging events, it may be helpful to lower the minimum severity at which `Eventd` will log from the default level of `WARN`.
  To change this setting, edit `OPENNMS_HOME/etc/log4j2.xml` and locate the following line:
  
  [source,xml]
  ----
          <KeyValuePair key="eventd"               value="WARN" />
  ----
  
  Changes to `log42.xml` will be take effect within 60 seconds with no extra action needed.
  At level `DEBUG`, `Eventd` will log a verbose description of every event it handles to `OPENNMS_HOME/logs/eventd.log`.
  