Deployment Architecture

Best Practice forward search head to indexer but dispatch folder fills -how to not forward dispatch

medunmeyer
Explorer

I am setting up distributed deployment monitor and trying to follow the Best Practices of sending the search head internal data to the indexers but using the basic recommended outputs.conf it also forwards the files in the dispatch folder to the indexer. I have very limited space for this folder on the indexer. How do you not forward the dispatch folder?

Thanks

0 Karma

medunmeyer
Explorer

Thanks all - I ended up expanding the /opt partition - thanks lguinn you.

0 Karma

lweber
Path Finder

guessing, that the files you are referring to are the app bundles replicated to search peers... and not indexed data.

if true, you can blacklist the files you do not want to be replicated in distsearch.conf

see also: https://docs.splunk.com/Documentation/Splunk/6.5.0/Admin/Distsearchconf#REPLICATION_BLACKLIST_OPTION...

hope this helps.

0 Karma

lguinn2
Legend

outputs.conf does not control what is forwarded, only where the data is sent.
It should not be forwarding the dispatch directory. The internal logs are found in $SPLUNK_HOME/var/log/splunk

Can you post the outputs.conf and the inputs.conf that you are using?

0 Karma

medunmeyer
Explorer

sorry I ment distributed monitoring console-

0 Karma
Get Updates on the Splunk Community!

What the End of Support for Splunk Add-on Builder Means for You

Hello Splunk Community! We want to share an important update regarding the future of the Splunk Add-on Builder ...

Solve, Learn, Repeat: New Puzzle Channel Now Live

Welcome to the Splunk Puzzle PlaygroundIf you are anything like me, you love to solve problems, and what ...

Building Reliable Asset and Identity Frameworks in Splunk ES

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