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?

[PankajK79]

I have read few posts/articles/docs around related to your concern, hope these might help:

• https://www.servicenow.com/community/itom-articles/9-steps-to-servicenow-integration-with-solarwinds...
• https://www.servicenow.com/community/itom-blog/take-your-solarwinds-integration-to-the-next-level-wi...
• https://www.servicenow.com/docs/r/it-operations-management/event-management/ci-binding-alert.html

[Nishant8]

Hello @Durgaprasad Joi, Since you are able to pull the data from SolarWinds, you can thoroughly analyze the incoming payload and map the data according to your system requirements. You can also enrich/transform the data in ServiceNow to handle missing fields.

Regards,

Nishant

[Durgaprasad Joi]

Can't we do any customisation in Java script on filed mapping for SRM Events?

[Nishant8]

Hello @Durgaprasad Joi, Yes, you can. However, I strongly recommend avoiding scripts, as the event table processes high volumes of records and a heavy script could impact performance later. You can certainly configure the field mapping according to your requirements.

If you share the details of your current roadblock, along with the inputs received from SolarWinds (making sure to mask any sensitive information), I can help you find a solution.

Regards,

Nishant