Splunk Search

Using Fields Efficiently

peasead
Path Finder

I'm trying to get a search to run as efficiently as possible and a couple of the guys on my team have been going back and forth regarding the placement of the 'fields' syntax.

I have always put the 'fields' syntax immediately after my sourcetype, but some people put it in the middle of the search, some put it before/after the math that is done, some put it right before the 'stats', 'table', etc.

I looked in the documentation, but I didn't see anything saying that it should go "here" or "there".

Is there a preferred place to put the 'fields' syntax?

1 Solution

yannK
Splunk Employee
Splunk Employee

If you really want to go that way, use the search inspector (the "i" button) to see the search speed.
and run the same search on the same time window with several variations of your search.

View solution in original post

yannK
Splunk Employee
Splunk Employee

If you really want to go that way, use the search inspector (the "i" button) to see the search speed.
and run the same search on the same time window with several variations of your search.

peasead
Path Finder

Great idea.

As it turns out, it doesn't matter much.

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!

Fuel Your Journey: What’s Waiting for You at the .conf26 Acceleration Station

Navigating the show floor at .conf26 isn't just about keynotes and technical breakout sessions; it's also ...

Join the Final Session of the Data Management & Federation Bootcamp Series

Over the past three sessions of the Data Management & Federation Bootcamp Series, we've explored how to build ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...