Skip to:

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

Add foreignSource and foreignId parameters when sending events as an alternative to nodeId

Description

Currently the forceRescan event requires the OpenNMS nodeid. We request that the forceRescan event be extended to support specifying the node to be rescanned by providing the foreignSource and foreignId of the node.

When external systems initiate activities that require a node rescan, these systems will in general not know the (internal) OpenNMS nodeid. In our case, our ERP (Netsuite) knows 'everything' about our equipment inventory and generates the foreignSource and foreignId.

Most OpenNMS REST APIs that require a nodeid also support FS:FID. We'd like to be able to initiate a forced rescan the same way.

Thanks,
John Black

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Benjamin Reed September 20, 2017 at 1:04 AM

Yeah, since it went into the 2017 foundation branch.

John Blackburn September 19, 2017 at 12:59 AM

Will this update make it into 20.1?

John Blackburn August 17, 2017 at 10:44 PM

Thanks.  Looking forward to when this is available in general release.

Alejandro Galue August 17, 2017 at 12:25 PM

Hi , yes the solution for this one is the same solution for . The handling of these 2 optional parameters is done inside Eventd, so no matter how you send an event to OpenNMS (send-event.pl, ReST API, XML through TCP 5817), the nodeId will be associated with the node if the incoming event doesn't have the nodeId populated, and the _foreignSource and _foreignId parameters are supplied and have a match on the database.

John Blackburn August 16, 2017 at 11:46 PM

Hi, I'm just wondering if  is related to/dependent on this issue.

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created September 26, 2016 at 11:48 AM
Updated February 15, 2018 at 8:55 PM
Resolved August 16, 2017 at 11:31 AM