Deployment Architecture

Which is better; HEC on heavyforwarder or clustered indexers for Kafka?

splunkreal
Motivator

Hello,

we plan to try Kafka as data collector and we'd like to know if we should keep our HF to receive HEC inputs for Kafka data or send directly to indexers, about 200-300gb per day?

Looks like HF is better for filtering before indexing.

Thanks.

 

* If this helps, please upvote or accept solution if it solved *
Labels (2)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

An HF is just an indexer that doesn't store data so it's no better or worse for filtering than an indexer.

A single HF is a single point of failure for your Kafka data.  It also can lead to poor data distribution which will negatively affect search performance.  The solution, of course, is to have multiple HFs, but if you're going to round-robin among HFs, why not just round-robin among indexers?

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

An HF is just an indexer that doesn't store data so it's no better or worse for filtering than an indexer.

A single HF is a single point of failure for your Kafka data.  It also can lead to poor data distribution which will negatively affect search performance.  The solution, of course, is to have multiple HFs, but if you're going to round-robin among HFs, why not just round-robin among indexers?

---
If this reply helps you, Karma would be appreciated.
Get Updates on the Splunk Community!

Exciting News: The AppDynamics Community Joins Splunk!

Hello Splunkers,   I’d like to introduce myself—I’m Ryan, the former AppDynamics Community Manager, and I’m ...

The All New Performance Insights for Splunk

Splunk gives you amazing tools to analyze system data and make business-critical decisions, react to issues, ...

Good Sourcetype Naming

When it comes to getting data in, one of the earliest decisions made is what to use as a sourcetype. Often, ...