Knowledge Management

Forwardedindex Whitelist Routing

ephemeric
Contributor

Greetz,

We have two summary indexes we would like to forward, so on Splunk 5.0.3:

[tcpout]

indexAndForward = true

defaultGroup = Client1, Client2

maxQueueSize = 7MB

useACK = true

# RTFM says below to disable defaults:

forwardedindex.0.whitelist =

forwardedindex.1.blacklist =

forwardedindex.2.whitelist =

# Then custom.

forwardedindex.0.blacklist = .*

forwardedindex.1.whitelist = .*_ext_summary

[tcpout:Client1]

server = 172.nn.nn.nn:9997

[tcpout:Client2]

server = 172.nn.nn.nn:9997

As per RTFM, whitelisting only allowed in top stanza.

At the moment, both groups get all forwarded summary indexes which is not what we want.

Is it possible to TCP route via a group for a whitelisted forwardedindex?

I have done _TCP_ROUTING for an input but don't see anything for an index?

We want to send client1_ext_summary out via Client1 group and client2_ext_summary out via Client2 group.

Thank you.

0 Karma

SarahSplunk123
Explorer

Hello,

You could do this via routing data from your indexes through props/transforms.conf to the outputs.conf.

Best regards

0 Karma
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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...