Configuring severity Event Field Mapping for a New Relic alert

Micael
Tera Contributor

After setting up a New Relic webhook and ingesting New Relic issues into Event Management, I'm unable to create alerts due to the error message: "Severity: Invalid value". Despite configuring the Event Field Mapping, the error persists. I've followed several ServiceNow articles but cannot find the mistake or missing configuration.

 

Any suggestion on Event Field Mapping from New Relic issues?

 

The New Relic field is the priority, as seen in both the New Relic Source and Target table created by SNOW out of the box.

4 REPLIES 4

J Siva
Tera Sage

Hi @Micael 
I believe we get "severity" value from the NewRelic not "priority".
So the source field should be "severity" and target field should be "priority".
Make sure that "priority" fields exists in the em_event table and also verify the type of the priority field. If its select box, then validate the choice list.

 

Hope this helps.
Regards,
Siva

Micael
Tera Contributor

J Siva, I attempted that approach without success. I also modified the To Values using the ServiceNow priority levels like Critical and Major, but it did not work.

Hi @Micael , Can i have a look at some demo data that is coming from New Relic(Probably a JSON payload). The event field mapping looks fine to me. Also, please share the snapshots of the event rule that is created to generate the alerts

Jeffreys Quinti
Tera Contributor

Hi Micael,

 

Please make sure that:
-Additional_info field of the New Relic events is a valid JSON format
-A field named "priority" is present in additional_info - watch out as it is case sensitive.
-Value provided from New Relic is "Critical" for key priority. Again it is case senstive.

 

Hope it helps