Getting Data In

Multiple Eventcodes in same Blacklist

helpmelearn
Explorer

Hello 

We are trying to change the below blacklists: 


blacklist3 = EventCode="4690" 
blacklist4 = EventCode="5145"
blacklist5 = EventCode="5156"
blacklist6 = EventCode="4658"
blacklist7 = EventCode="5158"

To a single blacklist with multiple eventcodes. We have tried:

blacklist3 = EventCode=5145,5156,4658,4690,5158

and

blacklist3 = EventCode="5145" OR "5156" OR "4658" OR "4690" OR "5158"

And none of these are applying and blocking out the event codes. 

 

Any recommendations on how to get this to work? 

 

Labels (1)
Tags (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

The syntax is incorrect.  A blacklist must be a comma-separated list of event IDs or pairs of key=regex specifiers.  Try this

blacklist3 = 5145,5156,4658,4690,5158
---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

The syntax is incorrect.  A blacklist must be a comma-separated list of event IDs or pairs of key=regex specifiers.  Try this

blacklist3 = 5145,5156,4658,4690,5158
---
If this reply helps you, Karma would be appreciated.

helpmelearn
Explorer

Thankyou! This worked 😄 

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 Enterprise Security: An Automated Phishing Response Workflow

Originally posted on Splunk.com.   Key takeaways  The volume of phishing emails can overwhelm even the most ...

Sharper ES Detections, Agentic AI Integrations, Smarter Workload Management, and More ...

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

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...