In OpenNMS you configure services for mainly two use cases:

• Run a test against service for availability and measure latency configured poller-configuration.xml

• Assign a service as entry point to gather performance data in collectd-configuration.xml

The services are assigned manually or through detectors and the service name is a loose convention between collectd, pollerd and the database.

It is possible to define services in poller-configuration and collectd-configuration which are never assigned in the database and you can have services in the database where no poller or collectd configuration exist.

The loose convention introduces configuration errors through typos and maintenance tasks over time.

To give administrators a possibility to identify those services, add a feature in the admin section "System Diagnostics" for example as "Monitoring Sevice Audit" and provide the following information:

• Services in poller-configuration.xml which are not assigned to a Nodes IP interface

• Services in collectd-configuration which are not assigned to a Nodes IP interface

• Services in the database which don't have a poller- or collectd-configuration

See example screenshot below.