Getting Data In

How set up forwarding on linux-to-linux


No firewall between forwarder A and indexer B. Both are Red Hat 2.6...

/opt/splunkforwarder/etc/system/local/outputs.conf on A (which has universal forwarder):

defaultGroup = default-autolb-group

server =

[tcpout-server://] <<< This is my indexer

On the indexer I have "manager -> Forwarding and receiving -> receive data" set to 9997

Are "/var/logs" natively set to be sent to the indexer? Or does this have to be configured?

Tags (1)
0 Karma

Splunk Employee
Splunk Employee


One thing to note here. You edited your default inputs.conf. This is generally considered bad practice. If you were to update your universal forwarder to a newer version, the update process would revert your change back to, as the name implies, the default.

Right at the top of the default/inputs.conf (as well as other default/*.conf files) there is a warning stating not to edit the file.

You need to make this change in the local inputs.conf. In /opt/splunkforwarder/etc/apps/SplunkUniversalForwarder/, there should be a local directory. In it, there may or may not be a inputs.conf file. If there is, great, make your changes there. If there isn't, just copy the inputs.conf from the default directory into the local directory. Then make your changes to the inputs.conf in the local directory.


The answer to this question, thanks to Ed Elisio, is to configure


on the forwarding device to be something like this if you're interested in /var/log stuff:


index = _internal

[monitor:///var/log] <<<<<<<< added this

Restart the universal forwarder, too.

0 Karma
Get Updates on the Splunk Community!

Happy CX Day to our Community Superheroes!

Happy 10th Birthday CX Day!What is CX Day? It’s a global celebration recognizing innovation and success in the ...

Check out This Month’s Brand new Splunk Lantern Articles

Splunk Lantern is a customer success center providing advice from Splunk experts on valuable data insights, ...

Routing Data to Different Splunk Indexes in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. The OpenTelemetry project is the second largest ...