Getting Data In

what is the difference in configuration between forwarders for receiving and sending

windyita
New Member

I have read another Q&A
http://answers.splunk.com/answers/50082/how-do-i-configure-a-splunk-forwarder-on-linux
but I'm confused whether the steps should be done on the receiver or the sender.
thanks in advance

Tags (2)
0 Karma
1 Solution

MuS
SplunkTrust
SplunkTrust

Hi windyita,

universal forwarder is the sender and indexer is the receiver, so

  • Steps 1-3 are obviously done on the universal forwarder
  • Step 4 is done on the indexer which is the receiver, if it has not been done before. This is a one time action.
  • Steps 5-7 are done on the universal forwarder

hope this helps ...

cheers, MuS

View solution in original post

0 Karma

MuS
SplunkTrust
SplunkTrust

Hi windyita,

universal forwarder is the sender and indexer is the receiver, so

  • Steps 1-3 are obviously done on the universal forwarder
  • Step 4 is done on the indexer which is the receiver, if it has not been done before. This is a one time action.
  • Steps 5-7 are done on the universal forwarder

hope this helps ...

cheers, MuS

0 Karma

windyita
New Member

I actually did as what you have said, but in step 7:
Step 7: Add Data:

/opt/splunkforwarder/bin/splunk add monitor /path/to/app/logs/ -index main -sourcetype %app%

This will create a file: inputs.conf in /opt/splunk/etc/apps/search/local/

Note: System logs in /var/log/ are covered in the configuration part of Step 7. If you have application logs in /var/log/*/

I didn't find inputs.conf in /opt/splunk/etc/apps/search/local/

What is the reason ? thx

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!

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...

Level Up Your Workflow: Mastering Splunk Cloud Management via Terraform

Tech Talk Recap   From Chaos to Control: Scaling Splunk Cloud with Infrastructure as Code Managing apps in ...