All work
- Enrich content of nodeAdded eventNMS-12526Resolved issue: NMS-12526Marcel Fuhrmann
- Configurable index name for Event & Alarm ForwarderNMS-12082Resolved issue: NMS-12082Jesse White
- rearmingAbsoluteChange event is missing in default configNMS-10443
- default event description is incorrectNMS-10346Resolved issue: NMS-10346Patrick Schweizer
- Request ability to filter in Events on vabinds using an ET varbind name, rather than its order number(vbnumber)NMS-9892
- Config-tester not validating varbind matching in event filesNMS-9821Resolved issue: NMS-9821Patrick Schweizer
- IOActive: Cross-Site Scripting in createFavorite filter ParameterNMS-9670Resolved issue: NMS-9670Markus von Rüden
- Display AlarmId on Event pageNMS-8445Resolved issue: NMS-8445Markus von Rüden
- INFO-severity syslog-derived events end up unmatchedNMS-8106Resolved issue: NMS-8106Jeff Gehlbach
- Event definition file for JUNIPER-IVE-MIBNMS-8071Resolved issue: NMS-8071Cyrille Bollu
- Enable scheduled outages to apply to eventsNMS-7927
- "Noon" in search doesn't function correctlyNMS-7757
- REST API - Exception when searching events with timestampNMS-6606Resolved issue: NMS-6606Benjamin Reed
- REST API - Exception when getting events of a deleted nodeNMS-6605
14 of 14
Enrich content of nodeAdded event
Fixed
Description
Acceptance / Success Criteria
None
Lucidchart Diagrams
Created February 13, 2020 at 7:37 PM
Updated March 26, 2020 at 6:05 PM
Resolved March 26, 2020 at 6:05 PM
The event only says A new node (nodeLabel) was discovered by OpenNMS. in the log message and event description.
I would suggest to have different content in logmsg and description and also discovered is the wrong word because not only nodes that were discovered by the discovery trigger this event.
My suggestion:
logmsg: A new node (nodeLabel) was added.
descr: The node (nodeLabel) was added and is now being monitored.
operinstruct: This event is purely informative. Please make sure that the newly added device $LINK_TO_NODE_PAGE is monitored as desired.