Issues

Inform users when an ip-service of a business service is deleted

A BS hierarchy can be set to a view only mode

Provide detectors in the default foreign source for each service defined in poller and collectd configuration

Add support for a new edge type, used for intermediary map/reduce results

ActiveMQ logs to eventd.log

BSs are temporal (they can be replayed in time)

Business Rules (BR) can be written to control state of each BS

BSs have a ReST API for control such as activation, deactivation, external state change

Setup MDC logging

BS can be switched on and off with states such as: activated and deactivated

Users can run reports for any specified BS

Users can escalate the state (awareness/impact) of BPs

BSs can be given geographical coordinates for display in the OpenNMS geographical map

Users can request several standard actions of a BS: activation, refresh/recompute, delete, etc.

Create business service edges from the alarm details page

Create Vagrant box with Horizon 18 and Grafana 3.0

Users can acknowledge the state of a BS

BSs trigger events when their state changes in “live mode”

Users can view acknowledged vs unacknowledged (outstanding) problems states of BSs

Users can view the underlying supporting network topology of a BS

Adding edges is very slow and difficult to use when there are a large number of elements

Add support for using Business Services in Path Outages

BSs have a group based security model similar to the OpenNMS node security model based on categories

Deduplicate dependenices in the core and default packages

BSs can be configured with a Nagle’s algorithm style threshold for evaluating state, RC, and BIA to reduce the number or RC and Impact analysis events generated

Improve the out-of-box user experience

Business Services provide a higher level of monitoring using correlation business rules logic

Business Services can be provisioned

Business Services and be viewed in a tree based hierarchical layout in the STUI

Modularize Poller Monitors

Update repo scripts

The Business Service Monitoring feature integrates with OpenNMS and external systems

The Business Service Monitoring component provides report templates

Issues related to the Minion Java runtime, Karaf container and system packages

Enrich the event with information what changed business service

Users can query the state of a BS hierarchy.

Suppress business service events based on the hierachy

Add related topology information to a BSM

Handling of multiple Business Service Hierarchies

Aggregate the leafs with numbers instead of showing all of them in the view

Validate that the JMX collection definitions we have for 2.1x also work with 3.0.x

Write blueprint for Minion handler for syslog messages

Move distributable monitors into features/poller/monitors/core

Discovery's UnmanagedInterfaceFilter needs to be location-aware

Create blueprint-trapd-handler-default.xml

Syslog listeners use different default ports

Make location editable via provisioning UI

Write a Minion feature definition for opennms-poller-monitors-core

Move TrapNotificationListener interface from Trapd to TrapReceiverSnmp4jImpl