Splunk Search

Exclude a result in search

djras123
Observer

I am trying to exclude this from a search. They are almost all the same just the sshd instance changes can someone help me exclude?

ras1-dan-cisco-swi error: PAM: Authentication failure for illegal user djras123 from 192.168.1.2 - dcos_sshd[17284]
ras1-dan-cisco-swi error: PAM: Authentication failure for illegal user djras123 from 192.168.1.2 - dcos_sshd[29461]
ras1-dan-cisco-swi error: PAM: Authentication failure for illegal user djras123 from 192.168.1.2 - dcos_sshd[4064]
ras1-dan-cisco-swi error: PAM: Authentication failure for illegal user djras123 from 192.168.1.2 - dcos_sshd[9450]

Thanks guys besides excluding each one,

Labels (1)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

While you could do an explicit exclusion as @marnall already showed it's probably not the most effective solution. Remember that by default inclusion is better than exclusion.

So the question is whether the events you want to exclude differ significantly from those you include? (Of course the best thing would be if you could differentiate them by an indexed field).

0 Karma

marnall
Motivator

While not the most computationally efficient, you could use a negating keyword search for the string you would like to exclude:

<yourSPL> NOT "PAM: Authentication failure for illegal user djras123 from"

Or have it on a separate search line, if your SPL does not end on a "search" command:

<yourSPL>
| search NOT "PAM: Authentication failure for illegal user djras123 from"
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 ...