Fixed
Details
Assignee
Christian PapeChristian PapeReporter
Marcel FuhrmannMarcel FuhrmannHB Grooming Date
Sep 01, 2020HB Backlog Status
BacklogSprint
NoneFix versions
Affects versions
Priority
Minor
Details
Details
Assignee
Christian Pape
Christian PapeReporter
Marcel Fuhrmann
Marcel FuhrmannHB Grooming Date
Sep 01, 2020
HB Backlog Status
Backlog
Sprint
None
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created February 7, 2019 at 8:27 AM
Updated September 22, 2020 at 11:01 AM
Resolved September 22, 2020 at 11:01 AM
The event is not useful in its current state.
It should contain more information like:
foreignId
nodeLabel
ipaddr
location
Edit:
I've tested the variables below in a nodeDeleted event and no one resolved a value. I guess the values are not known any more because ONMS deletes first and then creates the event.
Here an example how the new content could look like:
LogMsg:
Node %nodelabel% was deleted
Description:
%nodelabel% in location %location% was deleted from requisition %foreignsource%.
This can have multiple reasons.
OpenNMS default config will delete any node that is down for seven consecutive days
It was removed from the corresponding requisition /opennms/admin/ng-requisitions/index.jsp#/requisitions/%foreignsource%. This can be done manually using the web ui or using provisiond import schedules.
It was manually deleted using the "delete node" /opennms/admin/deleteNodes menu.
It was removed using the API
Operator Instructions:
Please verify if the deletion was planned.