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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...