Return-Path: X-Original-To: apmail-stratos-dev-archive@minotaur.apache.org Delivered-To: apmail-stratos-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3552E17354 for ; Wed, 20 May 2015 20:36:56 +0000 (UTC) Received: (qmail 53599 invoked by uid 500); 20 May 2015 20:36:56 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 53549 invoked by uid 500); 20 May 2015 20:36:56 -0000 Mailing-List: contact dev-help@stratos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stratos.apache.org Delivered-To: mailing list dev@stratos.apache.org Received: (qmail 53527 invoked by uid 99); 20 May 2015 20:36:55 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2015 20:36:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 4BB78C6F90 for ; Wed, 20 May 2015 20:36:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.901 X-Spam-Level: ** X-Spam-Status: No, score=2.901 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=wso2.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id lP3l_X3QNKT5 for ; Wed, 20 May 2015 20:36:45 +0000 (UTC) Received: from mail-yh0-f42.google.com (mail-yh0-f42.google.com [209.85.213.42]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 06F7C20C38 for ; Wed, 20 May 2015 20:36:44 +0000 (UTC) Received: by yhrr66 with SMTP id r66so16157414yhr.3 for ; Wed, 20 May 2015 13:36:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ZTRlL16sxZocP2qYvHpnDth+Fmd/b1ofV0YWhTwzUJo=; b=L6rM1LsdhBnvMZQybEvBH1zhKyxZkBAV19WXLvO69smFtWmpHsxyk44CD4DNM0m9NP efeLQcnFjw51kqINfTy603F84/aFnpbK/PrAH3n+JKxG3r9BZGgSwEp1/mDpXavpnrAo UrSRtDlYqODvTy9lL0nDd0ALTkOmQPCIlgr/A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=ZTRlL16sxZocP2qYvHpnDth+Fmd/b1ofV0YWhTwzUJo=; b=dK6Ut+VHJA8OdRrfo5snd9oX4t7WInFvQgrpsB3wMau+wvtOMb49zgd1yLn9ZTtaSo nG97GxY/S0hX69NCHoXpLJb6QD78tu05HZDykI5gt+y3vsbZAXUfPCO5wEDkrIklhABs 4MNdtDqWUC0PsLgO1E4E64NTuSsgfDGlnm8zSHGMoQl+TdqgyAOPgEDpOQFRjPc1rA4H ieM2mDyW4ur01Ll6Yxdy3kzrAop2l7a1yDvmuK7/0ho/evMNm2rTRjiK8jDfyxi8xhNg Pu333ez56JIV56hDRa7aRKVmiWGAKap3/SRnGvBV6u8OjhoFOf/Vm/72ZmRV2POgcbfS /Hcg== X-Gm-Message-State: ALoCoQl+0UdlUx4dFMF0Fzb59eT822dVA2X+IdyaCzmABprHTWNfdSCcBLxEWUVkVcCLrIrhWIWn MIME-Version: 1.0 X-Received: by 10.170.215.69 with SMTP id h66mr36788413ykf.74.1432154197420; Wed, 20 May 2015 13:36:37 -0700 (PDT) Received: by 10.129.71.86 with HTTP; Wed, 20 May 2015 13:36:37 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 May 2015 02:06:37 +0530 Message-ID: Subject: Re: [Discuss] PCA - Log Event Publishing to BAM From: Rajkumar Rajaratnam To: "dev@stratos.apache.org" Content-Type: multipart/alternative; boundary=001a113bcfa033870f051689627e --001a113bcfa033870f051689627e Content-Type: text/plain; charset=UTF-8 Thanks for the info Chamila! On Wed, May 20, 2015 at 7:19 PM, Chamila De Alwis wrote: > Hi Raj, > > Please find my comments inline. > > On Wed, May 20, 2015 at 6:57 PM, Rajkumar Rajaratnam > 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 > > > -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr.com --001a113bcfa033870f051689627e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks for the info Chamila!

On Wed, May 20, 2015 = at 7:19 PM, Chamila De Alwis <chamilad@wso2.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
H= i Raj,

Please find my comments inline.

On Wed, May 20, 2015 at 6:57 PM, Rajk= umar Rajaratnam <rajkumarr@wso2.com> wrote:
Sorry I am not up-to-d= ate 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), ho= wever any specified log file location will be scanned.
=C2=A0
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-balan= cing 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 fa= il-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 conce= pt implemented? For example, publish events to CEP cluster in a load-balanc= ing 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 featu= res. Currently no multiple Thrift receiver concept is implemented, and ther= e are no WSO2 Carbon DataBridge like event queuing in the Thrift publisher.= The Java Cartridge Agent makes use of the WSO2 Carbon's DataBridge, th= erefore it can handle multiple Thrift receivers. I'm not sure of the lo= ad balancing functionality of the Carbon DataBridge. I agree that these are= some interesting and important features that need to be included, so
=
=C2=A0=C2=A0

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





--
<= div dir=3D"ltr">
Rajkumar Ra= jaratnam
Committer & PMC Member, Apache Stra= tos
Software Engineer, WSO2

Mobile : +94777568639
--001a113bcfa033870f051689627e--