Business Service Daemon The Business Service Monitoring Daemon (BSMD) handles calculation of the operational status of the defined business services. The daemon tracks the operational status of all business services and sends events when there are operational status changes. To calculate the operational status, the BSMD evaluates the reduction key of alarms from associated business service edges. This means that the alarm’s reduction key of a defined business service must not change afterwards, otherwise BSMD will not be able to calculate the operational status correctly. This also applies for removing the alarm data from events associated to business services. In addition, the child type "IP Service" from the Business Service Configuration Page requires events with the default reduction keys being defined: * uei.opennms.org/nodes/nodeLostService * uei.opennms.org/nodes/nodeDown * uei.opennms.org/nodes/interfaceDown Every time you make changes to the configuration of a business service, you must reload the daemon’s configuration. 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. Reload the BSMD configuration with any of the following mechanisms: Click the Reload Daemon button in the Business Service Editor. Send the reloadDaemonConfig event using send-event.pl or use the "Manually Send an Event" UI with parameter daemonName bsmd. Use the REST API to perform a POST request to /opennms/api/v2/business-services/daemon/reload. When the reload of the configuration is complete, an event of type uei.opennms.org/internal/reloadDaemonConfigSuccessful is generated. Example reloading bsmd configuration from CLI $\{OPENNMS_HOME}/bin/send-event.pl -p 'daemonName bsmd' uei.opennms.org/internal/reloadDaemonConfig Example reloading bsmd configuration through ReST POST curl -X POST -u admin:admin -v http://localhost:8980/opennms/api/v2/business-services/daemon/reload Reduce Functions Topology