Splunk Search

fields order when using splunk search in command line

patrice_boodhoo
New Member

I would like to have the same order of fields from the result when executing a search command from the user interface and from command line.

Eg when I execute
index=idx_lyl earliest=10/01/2014:0:0:0 latest=11/03/2014:23:59:59 criticity!=".Info" AND criticity!=".Debug" AND criticity!="*Notice" | timechart count by criticity | sort + _time

from the Splunk UI, the fields are in that order
"_time","-.Error","Daemon.Error","Daemon.Warning","Kern.Alert","Kern.Critical","Kern.Error","Kern.Warning","Local4.Error","Local7.Error","Local7.Warning",OTHER

But when I ran the same search from command line the fields are in a different order ie
"-.Error","Daemon.Error","Daemon.Warning","Kern.Alert","Kern.Critical","Kern.Error","Kern.Warning","Local4.Error","Local7.Error","Local7.Warning",OTHER,"_time","_span","_spandays"

The search from command line being used is
splunk search "index=idx_lyl earliest=10/01/2014:0:0:0 latest=11/03/2014:23:59:59 criticity!=\".Info\" AND criticity!=\".Debug\" AND criticity!=\"*Notice\"
| timechart count by criticity | sort + _time" -preview 0 -maxout 0 -output csv > result.csv

Thanks

Tags (3)
0 Karma

fdi01
Motivator

To determine priority among the collection of fields resulting of an search in the CLI, Splunk uses ASCII sort order. Fields named "A" have a higher priority than fields named "B", and so on. Also, all fields with an uppercase letter have precedence over any fields starting with a lowercase letter, due to ASCII sort order.
this case that you have in CLI "-.Error","Daemon.Error","Daemon.Warning","Kern.Alert","Kern.Critical","Kern.Error","Kern.Warning",
"Local4.Error","Local7.Error","Local7.Warning",OTHER,"_time","_span","_spandays" is ASCII sort order.
but run this search in CLI:

    ./splunk search "index=idx_lyl earliest=10/01/2014:0:0:0 latest=11/03/2014:23:59:59 criticity!=".Info" AND criticity!=".Debug" AND criticity!="*Notice"
    | timechart count by criticity |table  "_time", "-.Error", "Daemon.Error", "Daemon.Warning", "Kern.Alert", "Kern.Critical", "Kern.Error", "Kern.Warning", "Local4.Error", "Local7.Error", "Local7.Warning", OTHER| sort + _time" -preview 0 -maxout 0 -output csv > result.csv

or
./splunk search "index=idx_lyl earliest=10/01/2014:0:0:0 latest=11/03/2014:23:59:59 criticity!=".Info" AND criticity!=".Debug" AND criticity!="*Notice"
| timechart count by criticity |fields "_time", "-.Error", "Daemon.Error", "Daemon.Warning", "Kern.Alert", "Kern.Critical", "Kern.Error", "Kern.Warning", "Local4.Error", "Local7.Error", "Local7.Warning", OTHER| sort + _time" -preview 0 -maxout 0 -output csv > result.csv

0 Karma

vasanthmss
Motivator

you can mention the field order using fields command,

your search .. | fields field1, field2, field3, field4....
V
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 ...

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Value Insights: Now Generally Available in the CMC

Organizations are under pressure to move faster, control cost, expand AI adoption, and prove value with more ...