Getting Data In

Where to make configuration changes in inputs.conf and outputs.conf on Linux?

ravisplunksap
New Member

Hi Team,

I have installed Splunk setup on one of my VM. On another VM I installed the Splunk universal forwarder to send the logs to Splunk Server.

I copied to make changes for inputs.conf and outputs.conf files to local folder to make changes because on default folder we shouldn't do changes.

So, they were so many attributes to make changes in both files. I am in confusion state.

Please tell me the basic values like where to insert host , source, sourcetype names, monitor file names, index name, etc in inputs.conf and where to give Splunk Server or Indexer IP, port number in outputs.conf.

Because i am setting up my test environment so that I wont do mistakes in my production environment .

Thanks & Regards,
Ravi

0 Karma
1 Solution

somesoni2
Revered Legend
0 Karma

ravisplunksap
New Member

thanks somesoni2

0 Karma

Richfez
SplunkTrust
SplunkTrust

This looked like it helped you significantly with your problem. I have converted this to an answer, If you agree it was helpful, could you mark it as Accepted? If not, ask some more!

0 Karma

ddrillic
Ultra Champion

It's hard to say where to start. Maybe at List of configuration files

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...