Getting Data In

Both universal forwarders have the same inputs.conf, but why is the index of data changing based on which machine it comes from?

nce054
Path Finder

I'm gathering data from two machines, and depending on which one it comes from, it has a different index. Both universal forwarders have the same inputs.conf which looks like

[monitor://C:\Windows\.marimba\MarimbaEndpointTuner\history-y*.log]
disabled=0
index = main
sourcetype = marimba

Can anyone think of a reason as to why they are being put in separate indexes?

0 Karma
1 Solution

nce054
Path Finder

Got the problem fixed. I went under appslearned and deleted all of the contents in each folder on the Universal Forwarders. Now, they both are coming up with an index of main. Thanks for the suggestion.

View solution in original post

0 Karma

nce054
Path Finder

Got the problem fixed. I went under appslearned and deleted all of the contents in each folder on the Universal Forwarders. Now, they both are coming up with an index of main. Thanks for the suggestion.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Check your indexer for transforms.conf rules that overwrite the index based on some criterion.

nce054
Path Finder

Got the problem fixed. I went under \apps\learned and deleted all of the contents in each folder on the Universal Forwarders. Now, they both are coming up with an index of main. Thanks for the suggestion.

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!

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...