route attribute in inputs.conf

splunkn — Fri, 05 Aug 2016 13:56:08 GMT

Can someone could explain the route attribute in inputs.conf

[splunktcp]
route = haskey..

What is matching rule here mentioned

Re: route attribute in inputs.conf

Jeremiah — Fri, 05 Aug 2016 14:24:43 GMT

The only time I've seen that setting used is when you want to re-parse cooked data. If you have data from a heavy forwarder going to an indexer, normally none of the indexer's index time props and transforms apply. This is because the data has already been 'cooked' (processed) by the heavy forwarder. You can change the route to force data to pass through parsing queues it would normally skip.

https://answers.splunk.com/answers/97918/reparsing-cooked-data-coming-from-a-heavy-forwarder-possible.html
https://answers.splunk.com/answers/305740/why-is-data-received-from-a-remote-splunk-instance.html
https://answers.splunk.com/answers/5528/forwarding-select-data-in-my-environment.html

Don't confuse this setting with more commonly used data routing settings, where you might want to forward some data to a 3rd party, to a different set of indexers, or drop a subset of events:

http://docs.splunk.com/Documentation/Splunk/6.4.2/Forwarding/Routeandfilterdatad

topic route attribute in inputs.conf in Getting Data In

route attribute in inputs.conf

Re: route attribute in inputs.conf