Getting Data In

Why does DBX prepend an escape character to double quotes when pulling JSON-formatted data from a table?

lagnone_splunk
Splunk Employee
Splunk Employee

My table has a column with JSON-formatted data that looks like this:

{"Message" : {"Field1": 1000, "Field2": 1000, "Field3": 1000, "Field4": 500, "Field5": 200, "Field6": 500, "Field7": 300, "Field8": 500}} 

But in Splunk, my raw event is coming in like this:

{\"Message\" : {\"Field1\": 1000, \"Field2\": 1000, \"Field3\": 1000, \"Field4\": 500, \"Field5\": 200, \"Field6\": 500, \"Field7\": 300, \"Field8\": 500}} 

Why is this happening and what can I do to correct it?

Tags (3)

btsay_splunk
Splunk Employee
Splunk Employee
DBX double quotes string data by default,  if this string content comes with “ in it, we replace them with \”.

In your case, the json string is with " in it, so they are all converted into \" as expected.

You may use the search language, perhaps as an eval expression, to remove the escape characters:

… | replace “\\""” with “\”” in message |…
… | eval message = replace(message, “\\””, “\”) | …

The advantage of eval statement is that it could be run via props/transforms.
0 Karma
Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...