Getting Data In

_TCP_ROUTING with clustered indexers system logs

splunkreal
Influencer

Hello,

we have 2 Splunk platforms and we are using _TCP_ROUTING to forward logs.

System logs from 1st platform indexers are currently logged on themself.

 

We want to also receive system logs from  indexers of the 1st platform on our 2nd platform however there is no default tcpout group on 1st platform indexers.

 

So should we create default outputs.conf on 1st platform indexers to continue indexing local system logs?

 

Thanks for your help.

 

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

tej57
Builder

Hello @splunkreal,

Yes, you'll need to define the outputs.conf on Indexers1 to forward the logs to indexers2. If you wish to send all the logs of indexers1 to indexers2, you can definitely use the defaultGroup parameter in outputs.conf. However, if you wish to send only a few logs from indexers1 to indexers2, it would be better to use _TCP_ROUTING in inputs.conf for those particular inputs.

 

Thanks,
Tejas.

---

If the above solution helps, an upvote is appreciated..!! 

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...