Skip to:

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

Add new parameter for DNSResolutionMonitor

Description

It seems the poller is only able to check the node-label. Often the label !=
node name.
For example we use the label to have a more understandable name and the node name is just the hostname.

hostname1 - srv-ads
hostname2 - srv-onms
hostname3 - srv-printserver

Sure, you could use these labels also as nodenames in general
But it makes also sense to be able to choose which name the DnsResolutionMonitor should check.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger August 9, 2017 at 4:09 PM

PR merged, marking as fixed.

commit 79eb3df019288929c2fcd79fb609717a19c43b38

Marcel Fuhrmann May 27, 2017 at 2:08 AM

And... there is something else. You have already started to improve the DNSResolutionMonitor... so you maybe could do this one, too? https://issues.opennms.org/browse/NMS-9249

Marcel Fuhrmann May 27, 2017 at 2:05 AM

With this config mode you have to build an own monitor for every node, correct? Might be useful in some scenarios, too.
But it was not my intention. But it's my fault because I used the wrong spelling. We should also have a switch which does "check nodeLabel / check foreignID". I use the foreignID field for the hostname. But these are usually useless, so I use the nodeLabel to give them useful names. But there is no need to check these useful labels because they don't exist in DNS.

Ron Roskens May 26, 2017 at 10:45 PM

Ron Roskens May 26, 2017 at 5:06 PM

Sorry, the lookup parameter is only for the DnsMonitor. I've fixed the title for the issue so it matches the actual java class name. (DNSResolutionMonitor vs DnsResolutionMonitor). I got confused because the case is different between the two.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Parent

PagerDuty

Created May 26, 2017 at 6:07 AM
Updated September 20, 2017 at 3:29 PM
Resolved August 9, 2017 at 4:09 PM