Skip to:

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

%interface% & %interfaceresolve% variables should resolve nodes managed IP address

Description

The current behaviour is described here: https://issues.opennms.org/browse/NMS-10637

 

In notifications you may want to have the IP address of a node. Which can be very difficult depending on the node.

In case of server nodes which often have only 1 IP interface, it's not hard to get this information. But what if you're dealing with switches which have many interfaces?

I can understand why interfaceDown or nodeLostService events are able to translate %interface% and %interfaceresolve% since there is a direct relation between the outage and the interface.

But it can look very different when nodeDown occurs (as I said, depending on the node).

 

My suggestion is to fill the variable with the primary managed IP interface of a node. This would fit to all kind of nodes.

 

 

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Christian Pape July 29, 2019 at 2:17 PM

Christian Pape July 29, 2019 at 2:13 PM

Can you please test if branch jira/ is working for you? You can use %primaryinterface% in notifications.

Christian Pape July 29, 2019 at 1:35 PM

I would prefer a solution where the field %interface% does not have two different meanings. How about another placeholder %primaryinterface% that always contains the primary IP address if it exists?

Fixed

Details

Assignee

Reporter

Labels

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created April 15, 2019 at 9:43 PM
Updated July 31, 2019 at 6:58 AM
Resolved July 31, 2019 at 6:58 AM