Getting Data In

Why are wildcards not working when configuring the source path in inputs.conf?

danillopavan
Communicator

I am facing issues with using wildcards in my input.conf file.

I am monitoring the same directory where 2 different files are being generated, and each one should be indexed in different source types.

Path: C:\Splunkfiles\faturamentoSAP\
File 1: splunk.YYYYMMDDHHMMSS_1.CSV
File 2: splunk.YYYYMMDDHHMMSS_2.CSV

The file 1 should be indexed in sourcetype 1, and file 2 should be indexed in sourcetype 2.

I have configured both sourcepath in "Data inputs » Files & directories" like below, but it is not working:

C:\Splunkfiles\faturamentoSAP\*1.CSV
C:\Splunkfiles\faturamentoSAP\*2.CSV

If I configure as "C:\Splunkfiles\faturamentoSAP" , it is bringing both files to the same source type, but that is not what i want.

How do I configure the source path using wildcards?

Many thanks and regards.

0 Karma

harsmarvania57
Ultra Champion

Hi @danillopavan,

If you have splunk server access in that case you can modify inputs.conf directly with below configuration.

[monitor://C:\\Splunkfiles\\faturamentoSAP\\]
whitelist = splunk\.\d{14}\_(?:1|2).csv

and props.conf as below

[source::C:\\Splunkfiles\\faturamentoSAP\\splunk.*1.csv]
sourcetype = sourcetype_1

[source::C:\\Splunkfiles\\faturamentoSAP\\splunk.*2.csv]
sourcetype = sourcetype_2

and then restart splunk service.

danillopavan
Communicator

Hello @harsmarvania57, thanks for your reply but in this moment i dont have backend server access.

Thanks and regards

0 Karma

harsmarvania57
Ultra Champion

In that case, could you please add 2 "Files & Directories", 1st with C:\\Splunkfiles\\faturamentoSAP\\splunk\.\d{14}\_1.csv and sourcetype sourcetype_1 & 2nd with C:\\Splunkfiles\\faturamentoSAP\\splunk\.\d{14}\_2.csv and sourcetype sourcetype_2

I had never tried using GUI but you can give it a try.

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...