Splunk Universal Forwarder - Route wineventlog to one output group and _internal to another I'm trying to configure a Universal Forwarder so that: wineventlog data is sent only to [tcpout:group1] _internal data is sent only to [tcpout:group2] Currently, wineventlog is routing correctly to group1, but _internal events are being sent to both group1 and group2. My goal is to stop _internal events from being forwarded to group1 and have them forwarded exclusively to group2. I've already tried overriding _TCP_ROUTING=* by setting _TCP_ROUTING = group2 on both the monitor://...splunkd.log stanza and the [splunkd] stanza, but _internal data is still being forwarded to both output groups. I've also reviewed Splunk's routing and filtering documentation, but I'm not sure what additional configuration is needed. What is the correct way to exclude _internal events from group1 while continuing to send them to group2? Is there a props/transforms-based routing configuration or another setting I'm overlooking?
... View more