Splunk Search

Row limit for custom commands

gpburgett
Splunk Employee
Splunk Employee

I've got a custom command that we're running over a large set of data. When I just run the part of the query up to right before the custom command, all of the data comes back. But as soon as I apply my command, only the first 50,000 rows are returned to the screen. Looking at the docks, I found that there is a "maxinputs" parameter in commands.conf, which I increased, and that searchresults::maxresultsrows in limits.conf also can have an effect, so I increased that as well. However, the search still only returns the first 50,000 lines. Is there another configuration that I'm missing that needs to be adjusted? Or is this a fixed limit that Splunk applies?

Tags (1)

gwobben
Communicator

This is probably not relevant any more but for anyone who's looking for this... I had chunked = true in my commands.conf and I got only 50,000 results. After setting this to false I got back all my results.

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!

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 ...