We are trying to route DB Connect data to a different indexer, however, the traditional method of adding _TCP_ROUTING to the inputs.conf (or even db_inputs.conf) and creating an output.conf file does not work. Is there any way to route data to more than one indexer from a HF running DB Connect?
Thanks
Had the same problem, figured it out, with some help from this:
https://answers.splunk.com/answers/452029/how-to-configure-http-event-collector-hec-with-tcp.html
DBConnect uses the HEC (HTTP Event Collector) to feed stuff into Splunk, and if you look at that doc, you'll see HEC doesn't use _TCP_ROUTING but uses a setting called optiongroup
to do the same thing (all lower case, unlike what the doc says...)
Anyway, in the inputs.conf
in the DBConnect app you'll see something like this for the events to point to HEC:
[http://db-connect-http-input]
disabled = 0
token = abcdefgh-1234-5678-9101-12345678901
First thing you need to do is create an outputs.conf
in the local/
directory for dbconnect (its syntax is the same as for regular routing using _TCP_ROUTING) - mine is basically this:
[tcpout:logother]
server = 10.1.1.1:4567
sendCookedData = false
Then the inputs.conf
gets updated to include an outputgroup
:
[http://db-connect-http-input]
disabled = 0
token = abcdefgh-1234-5678-9101-12345678901
outputgroup = logother
Unlike _TCP_ROUTING, I don't think outputgroup
lets you specify more than one destination (I tried, it didn't work), but you can put whatever in the outputs.conf stanzas to make it work.
when outputgroup is used in inputs.conf, all db_inputs will forward events to that outputgroup.
is there any way to forward events based on db input stanza.?
is there any way to forward events based on db input stanza.?
I wanted to forward all db inputs which have same source type to third party and below is the configuration I have made on Heavy forwarder.
outputs.conf
[tcpout:thirdparty]
server = server1:9997,server2:9997
props.conf
[oracle:audit:db]
TRANSFORMS-routing=route_db_thirdparty
transforms.conf
[route_db_thirdparty]
REGEX=.*
DEST_KEY=_TCP_ROUTING
FORMAT=thirdparty
I ended up using the method described in this link to route the data to a second indexer.
http://docs.splunk.com/Documentation/Splunk/6.6.3/Forwarding/Routeandfilterdatad
@bsanch2
Thanks.