Getting Data In

How to define specific Splunk indexers for different applications on the universal-forwarder?

scottroymcse
New Member

I have a requirement to log the default Windows logs using the universal forwarder to our main Splunk server, and then we have another application that needs to send logs to a different set of Splunk indexers.

I am pushing the applications to the UF host via a deployment server, however how do I specify that Application B use a different set of indexers?

I think I have a conflict in the outputs.conf when I have both Application A and Application B deployed to the UF host. The outputs.conf files are located in each of the /apps/ApplicationA/default and /apps/ApplicationB/default folders.

If I have just Application A or Application B pushed on their own, the required data is pushed to the correct Splunk indexer(s). Both installed at the same time ceases to send out anything.

0 Karma
1 Solution

esix_splunk
Splunk Employee
Splunk Employee

In your inputs.conf for the app, you can specify the index that the data source goes into. Something like:

inputs.conf in App A
[monitor:///appA-sourcetype1]
sourcetype=appA-logfile
index=appA_index


inputs.conf in App B
[monitor:///appB-sourcetype1]
sourcetype=appB-logfile
index=appB_index

It should be noted that if you have the same sourcetype defined across multiple apps, then your configurations will be read in lexicographical order.

View solution in original post

esix_splunk
Splunk Employee
Splunk Employee

In your inputs.conf for the app, you can specify the index that the data source goes into. Something like:

inputs.conf in App A
[monitor:///appA-sourcetype1]
sourcetype=appA-logfile
index=appA_index


inputs.conf in App B
[monitor:///appB-sourcetype1]
sourcetype=appB-logfile
index=appB_index

It should be noted that if you have the same sourcetype defined across multiple apps, then your configurations will be read in lexicographical order.

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!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...