Details
Assignee
UnassignedUnassignedReporter
Ronny TrommerRonny TrommerComponents
Affects versions
Priority
Major
Details
Details
Assignee
Unassigned
UnassignedReporter
Ronny Trommer
Ronny TrommerComponents
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created April 27, 2017 at 7:58 AM
Updated November 16, 2017 at 9:53 PM
OpenNMS provides an integration point for events which can be send into the system via TCP connection or ReST API. For the TCP connection the send-event.pl script is provided. If a user uses the send-event.pl or uses the ReST API to send a event to OpenNMS, the executing node needs to know the internal OpenNMS node ID and has to send it along with the event to make sure the event is associated with the correct node.
Every user which sends events into OpenNMS has to build custom script or code to implement a node ID lookup strategy to be able using this feature.
By default OpenNMS should have a default node id lookup strategy which can be configured to do a node ID lookup
by senders IP address (similar to Syslogd/Trapd)
by senders Hostname as a parameter or populated node label parameter
no node ID lookup
behaviour in case a lookup returns with multiple values could be not assigning a node id and make a WARNING in the log