topic Re: Filtering portions of log using heavy forwarder in Getting Data In

Filtering portions of log using heavy forwarder

Raghav2384 — Fri, 20 Mar 2015 16:00:00 GMT

Re: Filtering portions of log using heavy forwarder

cpetterborg — Fri, 20 Mar 2015 21:45:37 GMT

You may want to completely edit (or perhaps better - completely resubmit) this question. And don't use the code text tagging for the entire text so that you can have a reasonably viewable question that can contain the bold, etc. I'm not complaining or anything, but it is very hard to figure out what it is you want with it formatted as it is.

Re: Filtering portions of log using heavy forwarder

satishsdange — Mon, 23 Mar 2015 06:22:43 GMT

I agree with Cary's response.
Also its not mandatory to use HF if you want to filter raw logs. Indexer can very well do that. HF occupy one additional box & may become bottleneck in large deployment.

Re: Filtering portions of log using heavy forwarder

miteshvohra — Mon, 23 Mar 2015 07:28:41 GMT

Here is the link to Splunk Doc dedicated to the topic: http://docs.splunk.com/Documentation/Splunk/6.2.2/Forwarding/Routeandfilterdatad.

HF does not demand super-dome compute power and hence, it makes more sense to have a dedicated HF to filter data and give more headroom to the Indexer for its core function.