anchor.diff:  ----
   
   * Use the `Manually Send an Event` page of the web UI located in the admin section to send the event.
  -- Use the ReST API to perform a `POST` request to `opennms/api/v2/business-services/daemon/reload`.
  +* Use the ReST API to perform a `POST` request to `/opennms/api/v2/business-services/daemon/reload`.
   
  
positive.code: |===
  | Name            | Numerical code | Color / Code         | Description
  | `Critical`      | _7_            | Purple      / `#c00` | This event means that a severe service affecting event has occured.
  | `Major`         | _6_            | Red         / `#f30` | Indicates seriuos disruption or malfunction of a service or system.
  | `Minor`         | _5_            | Orange      / `#f90` | Used for troubles that have not immediate effect on service or system performance.
  | `Warning`       | _4_            | Yellow      / `#fc0` | An event has occurred that may require action.
                                                              This severity can also be used to indicate a condition that should be noted (logged) but does not require immediate action.
  
negative.code: | `Threshold`     | Uses the highest severity found more often than the given threshold.
  |===
  
  ==== Operational status changes
  
  If a _Business Service_ changes its operational status an _OpenNMS_ event of the type `uei.opennms.org/bsmd/serviceOperationalStatusChanged` is fired.
  The log message of the event contains the name of the _Business Service_.
  Additionally, the previous operational status and the new operational status are included.
  Please note, that this event has no node, interface or service associated.
  
  === Business Service Daemon
  
  Internally the _Business Service Monitoring_ feature is driven by the _Business Service Daemon_ (bsmd).
  It is responsible for tracking the operational status of all _Business Services_ and for sending events in case of operational status changes.
  Every time the configuration of a _Business Service_ is changed a reload of the daemon's configuration is required.
  This includes changes like the name of the _Business Service_ or its attributes as well as changes regarding the _Reduction Keys_, contained _Business Services_ or _IP Services_.
  
  ==== Reloading configuration
  
  A configuration reload can be initiated by an `uei.opennms.org/internal/reloadDaemonConfig` event with the parameter `daemonName` set to `bsmd`.
  If the reload of the configuration is done an event of type `uei.opennms.org/internal/reloadDaemonConfigSuccessful` is fired.
  The following options to trigger a configuration reload are available:
  
  * Use the `Reload` button on the `Manage Business Services` page in the administration section of the web UI.
  * Send the `reloadDaemonConfig` event directly to trigger the reload
  * Use the `send-event.pl` script
  
  [source,shell]
  