Getting Data In

Configuring inputs.conf to send data to specific Index

splunk_kk
Path Finder

I have a Splunk setup defined like: Universal Forwarder ---->Heavy Forwarder ------>Indexer

I need that all the logs hitting my Indexer should go to specific index. Which option is better:

1) Configuring index= new_index in Universal forwarder's input.conf
2) Configuring index= new_index in Heavy forwarder's input.conf
3) Configuring index= new_index in Indexer's input.conf

0 Karma

jtacy
Builder

Presonally, I would try to stick to setting this at the Universal Forwarder if possible. I don't think there's a significant processing cost to routing at the other tiers, but once you have a larger environment I think it would be a hassle to figure out why events are ending up in various indexes. I guess my philosophy is that if something can be done on the UF, that's probably the way to go.

That said, I probably wouldn't hesitate to select indexes on the HF or Indexer if I needed to make a change quickly and didn't have control of the UFs. If you ever want to select indexes based on something in the events themselves, such as the raw data, you're going to end up making that change on the HF or Indexer.

Good luck!

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

What Is Splunk? Here’s What You Can Do with Splunk

Hey Splunk Community, we know you know Splunk. You likely leverage its unparalleled ability to ingest, index, ...

Level Up Your .conf25: Splunk Arcade Comes to Boston

With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...

Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...

Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...