Splunk Search

| History & User

behymejt2012
Path Finder

Hi Everyone,

Utilizing | History to show all the Jobs running/completed is great, but I am unable to make a connection to who actually started the Job.

Does anyone have any suggestions to see what searches where performed by a user?

Thanks!

Tags (1)
0 Karma

aholzer
Motivator

Try using the index=_audit instead of "| history".

The _audit index contains a user field, an action field (that you should set to action=search, to only look at searches) and should show you the search run in the "search" field.

Something like:
index=_audit action=search search=* | table _time, search, user

You can also run stats and the like once you get the base search down.

Hope this helps.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

The history command only looks at your own past searches, it's what is used to compute the suggestions of recent searches that come up when you type.

In order to look at other users' searches you can inspect the _audit index. There are some pre-built searches in the SoS app, you can work your way from there or just start browsing the index, look for the field search - maybe saved_search as well.

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...