SolarWinds SRM Alerts – Field Mapping Failure Impacting CI Binding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
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
