Could someone confirm the expected outcome for the following settings: outputs.conf
[tcpout:group1]
server = 192.168.10.1, 192.168.10.2
sendCookedData = true
blockOnCloning = true
# Default block on cloning setting
[tcpout:group2]
server = 192.168.20.1, 192.168.20.2
sendCookedData = true
blockOnCloning = false
# Alternative blockOnCloning setting
inputs.conf
[monitor:////var/log/syslog]
index=linux
sourcetype=syslog
_TCP_ROUTING = group1,group2 1) If group1 is unavailable, but group2 is available 2) If group1 is available, but group2 is unavailable 3) If group 1 and group2 are both unavailable I have read the description in the spec file but am not sure how to correctly interpret it: blockOnCloning = <boolean>
* Whether or not the TcpOutputProcessor should wait until at least one
of the cloned output groups receives events before attempting to send
more events.
* If set to "true", the TcpOutputProcessor blocks until at least one of the
cloned groups receives events. It does not drop events when all the
cloned groups are down.
* If set to "false", the TcpOutputProcessor drops events when all the
cloned groups are down and all queues for the cloned groups are full.
When at least one of the cloned groups is up and queues are not full,
the events are not dropped.
* Default: true My end goal is to configure such that event if one TCPOUT group is unavailable logging should continue to the other unaffected, even if that means the unavailable group will miss receving some events. Thanks
... View more
