Getting Data In

How do I correct my forwarder blacklist configuration for FTP-Logs?

E_Andreas
New Member

Dear Community,

In our Webserver we have the following Logs: F:\IIS-Log
Sometimes we have F:\IIS-LOG\FTP and F:\IIS-LOG\WWW in this folder and sometimes the logs are stored on the Webserver without the FTP and WWW subfolders.

So we created following "inputs.conf" entry for our Windows-Webserver-APP (Deployment App):

[monitor://C:\inetpub\logs\LogFiles]
blacklist=*\FTP*$
index=winwebserver
sourcetype=iis
disabled=0

[monitor://F:\IIS-Log]
index=winwebserver
sourcetype=iis
blacklist=*\FTP*$
disabled=0

The Problem is, we still get the Logs from the F:\IIS-LOG\FTP\ Folder...
we need the * wildcard because sometimes the Logs are stored in F:\IIS-LOG\FTPSCV1\ folder etc.

How to correctly blacklist the FTP-Logs?

0 Karma

jaredlaney
Contributor

The blacklist actually needs to be a regular expression. Remember that "*" is a reserved character meaning zero or more. Could you try doing the following?

blacklist=FTP.*$ or maybe blacklist=FTP

Here are some more examples.
http://docs.splunk.com/Documentation/Splunk/6.2.0/Data/Whitelistorblacklistspecificincomingdata

You can test your regular expression at:

https://regex101.com/

0 Karma

E_Andreas
New Member

sorry i forgot the wildcard in the first post

blacklist=FTP*$
0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...