Getting Data In

JSON events with INDEXED_EXTRACTIONS making each extracted field multivalue

aknsun
Path Finder

Hi,

I have an issue with JSON events having multivalue fields.

We are using scripted input to ingest the data. The scripted input resides on the collector.

I have the following defined in the props.conf on the collector and no where else

[sourcetype_abc]
INDEXED_EXTRACTIONS = json
KV_MODE = none

Going through a few previous posts, it's being advised that KV_MODE = none need to be placed on the Search Head. Can someone confirm this? Do I also need to make use of AUTO_KV_JSON = false?

So does it need to be as follows:
On Collector

[sourcetype_abc]
INDEXED_EXTRACTIONS = json

On SH
[sourcetype_abc]
KV_MODE = none

Tags (1)
0 Karma
1 Solution

harsmarvania57
Ultra Champion

Hi,

Yes configuration which you provided is correct.

On Collector

[sourcetype_abc]
INDEXED_EXTRACTIONS = json

On SH

[sourcetype_abc]
KV_MODE = none

View solution in original post

harsmarvania57
Ultra Champion

Hi,

Yes configuration which you provided is correct.

On Collector

[sourcetype_abc]
INDEXED_EXTRACTIONS = json

On SH

[sourcetype_abc]
KV_MODE = none

aknsun
Path Finder

@harsmarvania57 Thanks. That worked.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...

Federated Search for Dynamic Data Self Storage Is Now Generally Available on Splunk ...

 Splunk is excited to announce the General Availability of Federated Search for Dynamic Data Self Storage ...

Index This | What has many keys but can’t unlock a door?

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