Getting Data In

Heavy, or Light?

jamesmcgee
Explorer

I'd like to deploy a light-forwarder to reduce footprint, but I need to send different inputs to a different index on the indexer.

i.e. OS logs, to osindex, DB logs to dbindex, Application logs to appindex.

No parsing or indexing needed locally, but am wondering if this can be achieved with a light-forwarder, or I need a heavy.

I tried to find this in docs, but not much luck.

Thanks in advance

1 Solution

jbsplunk
Splunk Employee
Splunk Employee

You can do this with a lightweight forwarder.

http://www.splunk.com/wiki/Where_do_I_configure_my_Splunk_settings%3F

You'd just need to specify in the input stanza something like

[stanza]
index = index_name

Since the LWF doesn't index anything, it will send to the index specified on the indexer.

If you didn't do this in inputs.conf, you could also use props/transforms in the place where the data is being parsed(indexer).

View solution in original post

jbsplunk
Splunk Employee
Splunk Employee

You can do this with a lightweight forwarder.

http://www.splunk.com/wiki/Where_do_I_configure_my_Splunk_settings%3F

You'd just need to specify in the input stanza something like

[stanza]
index = index_name

Since the LWF doesn't index anything, it will send to the index specified on the indexer.

If you didn't do this in inputs.conf, you could also use props/transforms in the place where the data is being parsed(indexer).

Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...