topic How to avoid influence of equal sign in text string when Splunk HEC parses JSON? in Getting Data In

How to avoid influence of equal sign in text string when Splunk HEC parses JSON?

cdp_fap — Wed, 03 Aug 2022 14:38:04 GMT

I was tring to ingest data into Splunk via HEC. One field of my data is:

myKey1 = " This is my Application message log, myKey2=myValue2 in the text." There is a Key=VALUE enclosed in the value of Field_name.

Splunk will parse the data into two key:

myKey1 = " This is my Application message log, KEY=VALUE in the text."

myKey2=myValue2

myKey2=myValue2 is part of the myKey1.

I don't want it. What I can do to avoid the influence of an equal sign in the text string?

Re: Splunk HEC parse json unexcepted when equal sign in string

dural_yyz — Wed, 03 Aug 2022 05:53:52 GMT

Question: Have you attempted the same search SPL in 'Fast Mode' vs 'Smart or Verbose Modes'. Part of the power of Splunk is how much it tries to help you. In this case the Search Head may be trying to auto detect fields for the user.

You could if required reduce the length of the event which field discovery will attempt, I believe default is ~10,000 characters to something much lower. However, I think that would overall be a poorer experience for your user base.