We have integrated Mulesoft with splunk and logs are sending to the heavy forwarder and indexing into "Main" index then forwarding to the indexers.
On Heavy forwarder we have created new index and assigned into the Http collector event but still logs are not indexing into the newly created index.
So do i need to create same new index on indexers as all indexers are in cluster mode.
The issue of the HEC events not being written to the newly created index on the HF is unrelated to the indexing tier. For the sake of clarity, can you confirm that you:
Remember, new created index may not be searched by default based on the index configuration and other RBAC setting.
EDIT: I moved this to a comment: ashpatel's answer is perfectly fine, so now that it's published it, he should get the credit here. 🙂 I didn't just delete the below because it could still be useful.
In fact, I think you need to do two additional things.
1) Create the index on your indexers. That's where the data is going, so that's where the indexes the data is going in to need to be.
2) Also you might need to edit the HTTP Event Collector and change it to allow it to index into that index. When you created it, if the index where these events are supposed to go you wouldn't have been able to pick it as an allowed index for that HEC to send events to, so you have to go back and reselect that again.
Then I think it should work.
Let us know how that goes!
Now we are getting mulesoft logs to newly created index on indexers but with other sourcetype also like syslogs . So we want to exclude sourcetype "syslogs" from newly created index.