Getting Data In

Heavy Forwarder outputs.conf settings not working as expected

dbturner18
Loves-to-Learn Lots

Greetings,

I am having issues with my heavy forwarder getting data into my indexers without having a local indexes.conf containing the index name.

I am doing all .conf work from the cli and not the webUI.   The issue is the "forwardedindex.filter.disbale=true" is not working as expected and I have to either:

1.  Create a local copy of the index I want to send to in indexes.conf

2. Add the index name to the whitelist setting for outputs.conf

Otherwise data does not get sent to the indexers.

Assistance please.

Here is my output.conf for example:

[tcpout]
defaultGroup = test_indexers
forwardedindex.filter.disable = true
indexAndForward = false


[tcpout:test_indexers]
#server = <ip address>:<9996>
server = x.x.x.x:9996,x.x.x.x:9996
disabled = false
sslPassword = <nope>
sslCertPath = $SPLUNK_HOME
sslRootCAPath = $SPLUNK_HOME

Labels (2)
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 ...