Alerting

udp://514 input exclusion

joeybroesky
Path Finder

We have logs coming in udp port 514 and want to exclude indexing events with the field "action" equaling "accept". We have tried inserting the following into the inputs.conf but does not work.

blacklist = action = "accept"

Please assist.

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

venkatasri
SplunkTrust
SplunkTrust

Hi @joeybroesky 

There seems no blacklist setting exist as per inputs conf - inputs.conf - Splunk Documentation

You can send the events to nullQueue to avoid indexing apply the following conf on HF/indexer. 

#props.conf
[your_udp_sourcetype/source::<source>/host::<hostname>]
TRANSFORMS-null= setnull
 
#transforms.conf
[setnull]
REGEX = action\s+=\s+\"accept\"
DEST_KEY = queue
FORMAT = nullQueue

 ----

An upvote would be appreciated and accept solution if it helps!

 

View solution in original post

venkatasri
SplunkTrust
SplunkTrust

Hi @joeybroesky 

There seems no blacklist setting exist as per inputs conf - inputs.conf - Splunk Documentation

You can send the events to nullQueue to avoid indexing apply the following conf on HF/indexer. 

#props.conf
[your_udp_sourcetype/source::<source>/host::<hostname>]
TRANSFORMS-null= setnull
 
#transforms.conf
[setnull]
REGEX = action\s+=\s+\"accept\"
DEST_KEY = queue
FORMAT = nullQueue

 ----

An upvote would be appreciated and accept solution if it helps!

 

joeybroesky
Path Finder

Thanks for your help! This did exactly what I was looking for.

0 Karma
Get Updates on the Splunk Community!

Splunk Enterprise Security 8.0.2 Availability: On cloud and On-premise!

A few months ago, we released Splunk Enterprise Security 8.0 for our cloud customers. Today, we are excited to ...

Logs to Metrics

Logs and Metrics Logs are generally unstructured text or structured events emitted by applications and written ...

Developer Spotlight with Paul Stout

Welcome to our very first developer spotlight release series where we'll feature some awesome Splunk ...