Hi guys,
one question.
We have a midsize Splunk environement. Data which is delivered to be ingested is increasing.
We need an architecture where we can handle our high performance data and on the other hand the normal data.
High performance data: high amount of data which needs to be ingested very fast ingested AND is under heavy search load from a specific known user group.
Are there any sugestions.
An idea is to separate data ingestion into differents streams like this :
+--------------------------------------------------------------+ | Loadbalancer (Ingress) | +--------------------------------------------------------------+ | | | +-----------------------+ +-----------------------+ +-----------------------+ | Forwarder Grp 1 / HEC | | Forwarder Grp 2 / HEC | |Forwarder Grp 3 / HEC | +-----------------------+ +-----------------------+ +-----------------------+ | | | +-----------------------+ +-----------------------+ +-----------------------+ | Indexer Cluster 1| | Indexer Cluster 2| | Indexer Cluster 3 | | (High-Performance IDX)| | (Normal IDX) | | High-Performance IDX)| +-----------------------+ +-----------------------+ +-----------------------+ | | | +-----------------------+ +-----------------------+ +-----------------------+ | Search Head Cluster | | Search Head Cluster | | Search Head Cluster | | for Power Users | | for OpenShift | | for Normal Users | +-----------------------+ +-----------------------+ +-----------------------+ | | | +-----------------------+ +-----------------------+ +-----------------------+ | Loadbalancer (SH1) | | Loadbalancer (SH2) | | Loadbalancer (SH3) | +-----------------------+ +-----------------------+ +-----------------------+
is this realisable ? Are there reference architectures with detailed descriptions about the other components and config items.
Best regards from switzerland
Sascha
... View more