Splunk Search

Why are my json fields extracted twice? (redux)

jamescrowley
New Member

I came across http://answers.splunk.com/answers/174939/why-are-my-json-fields-extracted-twice.html which seemed to describe perfectly the issue, but I've been unable to resolve - as far as I can see, KV_MODE is already set to none.

On our collectors, we have an app with props.conf as follows:

[fundapps_logs]
SHOULD_LINEMERGE = false
TIMESTAMP_FIELDS = datetime
TIME_FORMAT = %m-%d-%Y %H:%M:%S.%l
INDEXED_EXTRACTIONS = json
TRUNCATE = 20000
KV_MODE = none

however, we see two sets of fields in results when we search (but not for the built in splunk fields). If I then do

sourcetype=fundapps_logs | extract

I then see three sets of fields in results. I'm guessing I've got a config issue somewhere.

I've tried adding the same app and props.config to the splunk search/web head (everything runs on a single machine), and restarting but it doesn't appear to have any impact.

Any suggestion?

0 Karma

woodcock
Esteemed Legend

Did you deploy this to your Indexers and after that did you restart all Splunk instances on the Indexers?

0 Karma

somesoni2
Revered Legend

Not sure if you still have this problem, but the answer to this problem is here

https://answers.splunk.com/answers/301893/why-are-several-json-fields-getting-extracted-more.html

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Introduction to Splunk AI

How are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. Lucky for ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Maximizing the Value of Splunk ES 8.x

Splunk Enterprise Security (ES) continues to be a leader in the Gartner Magic Quadrant, reflecting its pivotal ...