Event Management - SCOM Severity Not Passing to ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2018 02:45 PM
Has anyone had trouble with payload information showing up as 'error' in Event Management? To be more specific, we are using the SCOM connector instance to connect our SCOM instance with service now, via a MID Server. While some events show up with a 'SCOM Severity' JSON pair equal to the Severity (Warning for example), others show up with a 'SCOM Severity' JSON pair as 'Error'.
I have double checked that the events showing up with 'SCOM Severity' of Error in SN actually have a defined Severity inside of SCOM (so the issue is not with the monitoring tool). Just struggling to understand why this value cannot be interpreted/transferred correctly for half of our events. Any insight/assistance would be greatly appreciated.
- Labels:
-
Event Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-19-2020 11:00 AM
This is a known bug in the SDK itself that I don't think will be fixed. You need to do a quick if statement check in the adapter code and translate it to the proper thing. That should get around it for you.