Getting Data In

setting destination index for win light forwarder

rgonzale6
Path Finder

We have a number of win machines to push splunk onto...basically, doing this:

msiexec.exe /i Splunk.msi SPLUNK_APP="SplunkLightForwarder" FORWARD_SERVER="IP:PORT" /quiet

The issue is, as I understand it if you don't tell a forwarding splunk instance the destination index, it defaults to main. We don't want the data in main. I know you can specify this in inputs.conf, but you can't seem to pass a 'index=__' argument to the msiexec install path above...and I'd like for this to be one step without changing any config files afterwards. Is this possible?

0 Karma
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

In general we don't recommend using MSI install flags to set configuration. Instead, install a passive Splunk forwarder using the flags, then copy over the relevant configuration files to set its behavior. Managing configuration this way is much more reliable and robust than relying on successful execution of a series of steps (e.g., what if the install succeeds, or partially completes, etc.)

Please see: http://www.splunk.com/wiki/Deploying_Splunk_Light_Forwarders

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

In general we don't recommend using MSI install flags to set configuration. Instead, install a passive Splunk forwarder using the flags, then copy over the relevant configuration files to set its behavior. Managing configuration this way is much more reliable and robust than relying on successful execution of a series of steps (e.g., what if the install succeeds, or partially completes, etc.)

Please see: http://www.splunk.com/wiki/Deploying_Splunk_Light_Forwarders

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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...