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
Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Dynamic formatting from XML events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...