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!

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

New Release | Splunk Cloud Platform 10.1.2507

Hello Splunk Community!We are thrilled to announce the General Availability of Splunk Cloud Platform 10.1.2507 ...

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...