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!

Splunk Search APIを使えば調査過程が残せます

   このゲストブログは、JCOM株式会社の情報セキュリティ本部・専任部長である渡辺慎太郎氏によって執筆されました。 Note: This article is published in both Japanese ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...