Getting Data In

Inputs hierarchy

fdesterke
New Member

Hello,

I want to monitor a directory but within that directory is another directory which I want to index under a different Source Type.

specifcally:
[monitor:///var/log/*]
sourcetype syslog

and the subfolder
monitor:///var/log/apache2/*
sourcetype apache_error

But the second input falls under the first, and since data isn't indexed twice, I'm wondering how splunk is going to handle this.
Will it just index the apache logs with the first rule with sourcetype syslog. Or is splunk smart enough to index the apache logs with the sourcetype apache_error if i define the second input like that.
Or do I put the apache data input before the other one?
Or do I blacklist the folder in the first input rule, if so, how?

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Use a blacklist within the first stanza to avoid indexing the Apache logs as syslog.

[monitor:///var/log/*]
sourcetype = syslog
# blacklist uses a regular expression, not a pattern
blacklist = (.*apache2.*)

[monitor:///var/log/apache2/*]
sourcetype = apache_error
---
If this reply helps you, Karma would be appreciated.
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!

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...