Getting Data In

How to configure different sourcetypes for logs in the same directory?

splunked38
Communicator

Hi,

I've got the following directory structure:

c:\Logs\<system>

At the moment, inputs.conf for application1 (search) is set to:

[monitor://c:\Logs\]
disabled = false
#host_segment 2 = system name
host_segment = 2
sourcetype = sourcetype1

The above config works.

However, I now have a requirement for another sourcetype. The system generates the logs into the same directory:

C:\logs\<system>\foo_sourcetype2.log

The inputs.conf for application2 named application2 will look like:

[monitor://c:\Logs\<system>\foo_sourcetype2.log]
disabled = false
sourcetype = sourcetype2

Unfortunately, this doesn't seem to be working.

I've also tried:

*blacklisting input.conf for application1 with: _sourcetype2.log - doesn't work

Thanks in advance.

0 Karma
1 Solution

somesoni2
Revered Legend

Try this in your inputs.conf

[monitor://c:\Logs\]
 disabled = false
 #host_segment 2 = system name
 host_segment = 2
 sourcetype = sourcetype1
blacklist = foo_sourcetype2\.log$

[monitor://c:\Logs\<system>\foo_sourcetype2.log]
 disabled = false
 sourcetype = sourcetype2

View solution in original post

somesoni2
Revered Legend

Try this in your inputs.conf

[monitor://c:\Logs\]
 disabled = false
 #host_segment 2 = system name
 host_segment = 2
 sourcetype = sourcetype1
blacklist = foo_sourcetype2\.log$

[monitor://c:\Logs\<system>\foo_sourcetype2.log]
 disabled = false
 sourcetype = sourcetype2

Luain
Engager

Cool. Thanks.

0 Karma

splunked38
Communicator

It seems that there was a (very long) delay after the restart, it was fine after it settled down.

The only addition as similar to @somesoni2:
blacklist = _sourcetype2.log

BTW: Can't add '$' on the regex as there are rotational logs in that directory

0 Karma

woodcock
Esteemed Legend

Make sure that the blacklist prevents the special files from being processed by the existing entry and then monitor the special files through a different path (be sure to have a good whitelist and blacklist here, too) by creating a soft link like this explains:

http://answers.splunk.com/answers/268433/data-input-path-name-is-the-same.html

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!

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...

Network to App: Observability Unlocked [May & June Series]

In today’s digital landscape, your environment is no longer confined to the data center. It spans complex ...

SPL2 Deep Dives, AppDynamics Integrations, SAML Made Simple and Much More on Splunk ...

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