Event Management - SCOM Severity Not Passing to ServiceNow

[Justin Wilburn]

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. 

 

[Vishal Khandve]

Hello Justin, Have you solved this problem. I'm facing the same issue. If you solved, can you please help me

[tauseef33]

Hi Guys,

I am also facing the same issue . 

will it be a problem if we change the scom groovy script?

Will populate scomSeverity with "Error" as critical severity instead of Major severity in ServiceNow.

[robertgeen]

No problem as this is a known bug on Microsoft side. I fixed this at another client by doing just this. Just know it will flag on changes when upgrades happen but this integration is pretty steady state at this point outside of new versions of SCOM. Thanks.

[mpmacconnell]

How did you fix this issue? Is it something we do on the Service Now side? Or was this a fix on the SCOM side? We are having the same issue.

[Omkar Mone]

We are facing the same issue, any update Justin?

Regards

Omkar