Hi Raj, Please find my comments inline.
On Wed, May 20, 2015 at 6:57 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > Sorry I am not up-to-date with this feature. > > 1) Is this publishing PCA's logs to BAM or Cartridge's logs to BAM? > The intention is to allow to publish service logs (eg: httpd.log), however any specified log file location will be scanned. > 2) Can it publish logs to more than one thrift receivers? > 3) Can it publish logs to more than one thrift receivers in a > load-balancing manner (1st event to 1st server and 2nd event to 2nd server)? > 4) Can it publish logs to more then one thrift receivers in a fail-over > manner (if sending to 1st server fails, then try to send it to 2nd server > and so on)? > 5) Is there any receiver groups concept implemented? For example, publish > events to CEP cluster in a load-balancing manner, while publish same events > to BAM cluster in a fail-over manner? Here CEP cluster is one receiver > group and BAM cluster is another one. > 6) Is there any event queueing mechanism implemented? What happens if > thrift receivers are not available? > Unfortunately, the Python Thrift publisher does not have these features. Currently no multiple Thrift receiver concept is implemented, and there are no WSO2 Carbon DataBridge like event queuing in the Thrift publisher. The Java Cartridge Agent makes use of the WSO2 Carbon's DataBridge, therefore it can handle multiple Thrift receivers. I'm not sure of the load balancing functionality of the Carbon DataBridge. I agree that these are some interesting and important features that need to be included, so > > If these are not implemented yet, we will create a JIRA and track this for > future release. > .. sounds good. :) Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com
