Getting Data In

Why is a specific file type still being indexed with my inputs.conf whitelist configuration?

mlaufenb
New Member

Here's my stanza:

[monitor:///opt/stash/logs/]
blacklist = \.gz$
disabled = false
followTail = 0
index = stash_pp
sourcetype = log4j
whitelist = (*access\.log$|*stash\.log$|*mail\.log$|*profiler\.log$|*debug\.log$|*plugin\.log$|*codesearch\.log$|\.out$)

I'm getting this file type atlassian-stash-access-2015-08-31.0.log which should have been excluded with the whitelist specification. Is there something wrong with the syntax?

Any help would be appreciated!

0 Karma

lguinn2
Legend

The proper regular expression for the whitelist is

whitelist = (.*access\.log$|.*stash\.log$|.*mail\.log$|.*profiler\.log$|.*debug\.log$|.*plugin\.log$|.*codesearch\.log$|\.out$)

The * alone just means "match an asterisk" in regular expressions. While Splunk does sometime allow a mix of globbing and regular expressions, don't do it here...

0 Karma
Get Updates on the Splunk Community!

Exciting News: The AppDynamics Community Joins Splunk!

Hello Splunkers,   I’d like to introduce myself—I’m Ryan, the former AppDynamics Community Manager, and I’m ...

The All New Performance Insights for Splunk

Splunk gives you amazing tools to analyze system data and make business-critical decisions, react to issues, ...

Good Sourcetype Naming

When it comes to getting data in, one of the earliest decisions made is what to use as a sourcetype. Often, ...