Getting Data In

Forwarder send Windows Events to different indexes

insidious
New Member

I have a universal forwarder pointed to the indexer cluster which sends Windows event logs. These events are sent to index "wineventlog" by default. I have a second universal forwarder which sends windows event log through an intermediate heavy forwarder connected to the indexer cluster. For some reason, these events are sent to index "main". There is no index specifier for the Windows events in any of the inputs.conf files. Why is this occurring and how do I get all of the events going to a single index (preferably "wineventlog")?

Tags (1)
0 Karma
1 Solution

somesoni2
Revered Legend

The default index for any input where index name is not specified in the inputs.conf is main. As a best practice I would explicitly specify the index name in all my data inputs.

To troubleshoot this you can run btool to see which index is being applied and from which conf file

$Splunk_Home/bin/splunk cmd btool inputs list --debug

Run this on both the Universal forwarders, search the attribute corresponding toyour WIndow event log and check the index name.

View solution in original post

somesoni2
Revered Legend

The default index for any input where index name is not specified in the inputs.conf is main. As a best practice I would explicitly specify the index name in all my data inputs.

To troubleshoot this you can run btool to see which index is being applied and from which conf file

$Splunk_Home/bin/splunk cmd btool inputs list --debug

Run this on both the Universal forwarders, search the attribute corresponding toyour WIndow event log and check the index name.

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