Skip to:

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

Split example poller package into components

Description

I would like to see the example poller package "example1" as distributed in poller-configuration.xml split into multiple packages. This will allow for flexibility of excluding certain hosts from certain scans without having to re-write the entire file. The motivation for this request for me is that auto-discovering a NetApp filer discovers an open port 80, but if HTTP is not licensed on the filer, OpenNMS incorrectly reports and HTTP outage since the filer returns a 503 on / with a page telling you to go to /na_admin/ for the web GUI.

Environment

Operating System: All Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Jeff Gehlbach February 9, 2011 at 2:16 PM

See note above, this is a don't-get.

Jeff Gehlbach February 9, 2011 at 2:15 PM

I think the subject of this issue creates confusion among the core committers, who are aware that there's an effort underway to enable the poller configuration to be split across multiple files, when that's not quite what the reporter is asking for. The default configuration files are intended as an example starting point, and already illustrate the concept of multiple packages (see the "strafer" package).

Addressing John, it's actually easier simply not to provision the unwanted services in the first place onto the nodes where they don't belong. The default Capsd configuration for HTTP should never detect an HTTP service if it receives a 503, and the default foreign-source for Provisiond should behave in the same way. If your system is finding an HTTP service in such a case then it's either a bug (possible as 1.8.1 came out a while ago and we've certainly fixed a few detector bugs since that time; please try to reproduce the issue with a current 1.8 release) or a misconfiguration. In the latter case, you can find help on the opennms-discuss mailing list to get things configured as they should be.

Matt Brozowski February 8, 2011 at 5:00 PM

I have marked this as 1.9.5 so the component owner can consider whether this is sensible or not

Won't Fix

Details

Assignee

Reporter

Components

Affects versions

Priority

PagerDuty

Created August 5, 2010 at 9:45 AM
Updated April 22, 2011 at 5:31 PM
Resolved February 9, 2011 at 2:16 PM

Flag notifications