SolarWinds SRM Alerts – Field Mapping Failure Impacting CI Binding

[Durgaprasad Joi]

Hello

When we pull alert trigger events from SolarWinds for storage devices, the system is unable to correctly map key fields such as node, metric name, and a few others. As a result, even though field mapping is configured, CI binding is not occurring for storage clusters.

Based on our discussion with the SolarWinds team, they are using SRM (Storage Resource Monitor) for defining storage device alerts. We believe that due to this, the out-of-the-box JavaScript is not effectively handling the field mappings.

Could you please advise if there is a solution to resolve this issue?

[Durgaprasad Joi]

Thanks for your support. As of now, we are able to bring information through filed mapping. However, we are also working on below solution provided by Hi support. 

'In SolarWinds Orion, associate your Storage Cluster objects with their parent Network Node so that NetworkNode is populated with a non-zero value for SRM alerts. Once this is done, the ServiceNow connector will automatically map the node value to the em_event.node field with no changes required on the ServiceNow side.'

[Durgaprasad Joi]

Solution Provided by Servicenow Hi Support

'In SolarWinds Orion, associate your Storage Cluster objects with their parent Network Node so that NetworkNode is populated with a non-zero value for SRM alerts. Once this is done, the ServiceNow connector will automatically map the node value to the em_event.node field with no changes required on the ServiceNow side.'