Splunk Search

Why does the REST Search in json format returns duplicate results?

chris94089
Path Finder

I'm performing a REST Search that ends with a | table command

When I configure the script to csv format, I get 5 events.  Raw format, 5 events. Splunk Web: 5 statistics/events.  But when I switch the format to json, 10 events, 5 of which are duplicates.  

Is there any valid reason why json should be any different than all the other types?

I've read solutions that suggest going to the config files, this is not available to me.

Hopefully, there is a way inline with my search to tell Splunk that I want, say,  just the data that shows up in my table.  This would be ideal.

Thanks so much.

Labels (1)
Tags (2)
0 Karma

to4kawa
Ultra Champion

https://docs.splunk.com/Documentation/Splunk/8.0.5/Knowledge/Automatickey-valuefieldextractionsatsea...

When KV_MODE is set to auto or auto_escaped, automatic JSON field extraction can take place alongside other automatic key/value field extractions. To disable JSON field extraction without changing the KV_MODE value from auto, add AUTO_KV_JSON=false to the stanza. When not set, AUTO_KV_JSON defaults to true.
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...