Getting Data In

Setting the index in props.conf

las
Contributor

I have a configuration with a log root with several log files, most of these are harmless, but one file contains confidential information.

logroot\loga.log
logroot\logb.log  
logroot\secure.log  

my inputs.conf monitors logroot.

I then use props.conf to set the sourcetype, but I would like to be able to route the secure.log to a different index.

Do I have to use a transform, and use ressources on my indexer, or could I specify this in either props og inputs.conf and do the selection on the universalForwarder?

1 Solution

yannK
Splunk Employee
Splunk Employee

An easier alternative is to define a special inputs on your specific file that will setup the destination index.
A stanza that has an exact path will have precedence over one with a wilcard.

[monitor://logroot\*.log]
sourcetype=mygenericsourcetype
index=mygenericindex

[monitor://logroot\secure.log]
sourcetype=myspecificsourcetype
index=myspecificindex

View solution in original post

las
Contributor

The files in the directory has different sourcetypes, so I need to set it on a per file basis.

0 Karma

yannK
Splunk Employee
Splunk Employee

An easier alternative is to define a special inputs on your specific file that will setup the destination index.
A stanza that has an exact path will have precedence over one with a wilcard.

[monitor://logroot\*.log]
sourcetype=mygenericsourcetype
index=mygenericindex

[monitor://logroot\secure.log]
sourcetype=myspecificsourcetype
index=myspecificindex

triest
Communicator

Just FYI the generic with a blacklist and then a more specific monitor does not work in Splunk 6. Support has said it was never officially supported but the rules were a bit lose and have been tightened in 6.

0 Karma

las
Contributor

Thanks, I will play around with this solution.

0 Karma

bmacias84
Champion

I would add a blacklist your generic monitor.


[monitor://logroot\*.log]
sourcetype=mygenericsourcetype
blacklist = secure.log$
index=mygenericindex
\
[monitor://logroot\secure.log]
sourcetype=myspecificsourcetype
index=myspecificindex

0 Karma

yannK
Splunk Employee
Splunk Employee

2 remarks :

0 Karma

las
Contributor

Yes, that is why, I wondered if it was possible to do it earlier in the process, as it is not a per event filtering, but a per file.

0 Karma

Ayn
Legend

Why are you using props.conf to set sourcetype? The easiest is to do this directly in inputs.conf. Same goes for index.

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!

Event Series: Splunk Observability Metrics Cost Optimization

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...