Splunk Search

default indexes to both target group

ansif
Motivator

How can we forward internal,_audit ,* indexes to both target groups?

In outputs.conf, create stanzas for each receiving indexer:

 [tcpout:systemGroup]
 server=server1:9997
 [tcpout:secutityGroup]
 server=server2:9997

In inputs.conf, specify _TCP_ROUTING to set the stanza in outputs.conf that each input should use for routing:

 [monitor://.../file1.log]
 _TCP_ROUTING = systemGroup
 [monitor://.../file2.log]
 _TCP_ROUTING = securityGroup

The above configuration help us to route events to seperate indexers, but how can we send internal indexes to both indexers?

Tags (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @ansif,
as I answered in the previous question, if you don't configure a default tcpout in outputs.conf and you don't insert _TCP_ROUTING in inputs.conf you send logs to all the tcpout configured stanzas
This doesn't consume license but consumes storage, so you have to understand if you really need or not duplicating internal logs (I don't think!).

Ciao.
Giuseppe

0 Karma

ansif
Motivator

Storage is not an issue since both parties(Security & Operations team works individually and license) need internal logs to troubleshoot.

Can I have an example configuration please? Can I just leave all Splunk internal indexes it is in the default dir
as it is to forward to both Indexer group or I need to create one default group?

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...