Splunk Search

Splunk: Query not returning all columns

itsmevic
Communicator

Hello,

 For some reason, my search is not returning all of the columns that I'd like to include in my search.  It's returning all of the columns EXCEPT "title" and "department".  Is there a limit to how many fields one can use? AND why would the columns noted not populate once the query is done?

index=* sourcetype=* "my keyword" 
| fields _time, user, src_user, action, EventCodeDescription, title, department
0 Karma

to4kawa
Ultra Champion
| makeresults count=1000
| streamstats count
| transpose 0 header_field=count

1000 fields are all right.

index=* sourcetype=* "my keyword" 
 | fields _time, user, src_user, action, EventCodeDescription, title, department

I think these fields may not be present in the event containing the keyword.

0 Karma

adonio
Ultra Champion

maybe those fields arent in the data when you use your keyword filter?
try to remove it, run the search in verbose and look on the fields on the left hand side, are title and department there?

efavreau
SplunkTrust
SplunkTrust

Related to adonio's requirement, make sure there's data in the fields, and ask for it before the first pipe. This will only get when all of them have a value. Example:
index=* sourcetype=* "my keyword" user=* src_user=* action=* EventCodeDescription=* title=* department=*

###

If this reply helps you, an upvote would be appreciated.
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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...