Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Include all plugins in default configuration

Description

Currently, there are many plugins in contributed to OpenNMS of which many new users are unaware. I recommend that we include references for all service plugins in the capsd-configuration.xml that gets installed by default. The reason we don't have them in the default installation is that they cause extremely long scan times. We should include them in the default configuration and set they're scan attribute to "off".

As part of this change, we need to have Capsd be aware of configuration changes and support an event for configuration changes. This could be done with the Capsd rewrite and/or the implementation of RESTFul configuration provisioning.

Environment

Operating System: All Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger May 14, 2015 at 4:46 PM

We recently revisited this list when we eliminated Capsd's code. If there are specific problems with the list of detectors, please open a new issue about it. Marking as fixed.

DJ Gregor July 31, 2008 at 10:30 PM

Some of the plugins take too long to scan because they don't implement a timeout and use the default OS TCP timeout. Fixing this would likely improve overall scan times, even if we enable all of the plugins.

Benjamin Reed July 31, 2008 at 2:55 PM

if we finish the OSGi stuff, we'll have each of them as a plugin and they'll be able to tell the protocol configuration GUI how to configure themselves... winking face

Tarus Balog July 31, 2008 at 2:52 PM

I prefer not to do this. The main reason is that newbie constantly complain that discovery takes too long as it is. Perhaps in the new GUI we can turn them on or something, but for now I'd like to leave this out. The main reason is to minimize capsd-configuration.xml changes but also to keep rescan times at a minimum.

David Hustace July 9, 2008 at 7:14 AM

Another reason for adding these services to the default configuration is that they could be configured for monitoring through the Provisioning Groups drop-down list of services.

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created July 9, 2008 at 7:12 AM
Updated May 14, 2015 at 4:46 PM
Resolved May 14, 2015 at 4:46 PM

Flag notifications