All Apps and Add-ons

Splunk automatically escaping the backslash character when creating/updating a snow ticket

michael3
Explorer

I'm trying to set the Description field of a ServiceNow Incident ticket through Splunk, and the string I'm passing contains a newline (\n).  But when Splunk creates/updates the ticket, either through the snowincident command or an action alert, it will automatically escape the backslash character.   So after Splunk passes the info to snow, the underlying json of the ticket looks like this:

{"description":"this is a \\n new line"}


and my Description field looks like this:

this is a \n new line

Is this something that Splunk is doing, or the ServiceNow Add-On?  Does anyone know of a way to get around this?

Labels (2)
0 Karma

magg
Observer

Also requesting a working way of adding newline to description in a servicenow incident generated by this addon

0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...