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 3988A17CDB for ; Wed, 20 May 2015 23:44:51 +0000 (UTC) Received: (qmail 60294 invoked by uid 500); 20 May 2015 23:44:51 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 60245 invoked by uid 500); 20 May 2015 23:44:51 -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 60235 invoked by uid 99); 20 May 2015 23:44:50 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2015 23:44:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5EEC9182753 for ; Wed, 20 May 2015 23:44:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.911 X-Spam-Level: ** X-Spam-Status: No, score=2.911 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=wso2.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id WuyvlswUOiGT for ; Wed, 20 May 2015 23:44:39 +0000 (UTC) Received: from mail-qk0-f170.google.com (mail-qk0-f170.google.com [209.85.220.170]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 62FCA45468 for ; Wed, 20 May 2015 23:44:39 +0000 (UTC) Received: by qkdn188 with SMTP id n188so38021011qkd.2 for ; Wed, 20 May 2015 16:43:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=nlEf6fVpL/g1nyMvAqzpbQNBcQLjkDjX0siGKdyDvgU=; b=UZ0elRjvOJFAKoqXV45x2+Nr7mfdmmxpN7NJpMxewwHrU6xomCgctpS3aoI2UnsJEA XZSne0kqrenZpRMMZpJK3Lf1oe85JzkXCAwSKD3mKpZbnrlOrFH0N/imgf5N+9mKNxxt Q5DI9yxKGaXawjBuvMVhz40ag94obfa9kiHBw= 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:from:date :message-id:subject:to:cc:content-type; bh=nlEf6fVpL/g1nyMvAqzpbQNBcQLjkDjX0siGKdyDvgU=; b=iZRyB1uZeEQRM0Ynn35Rh2kl18/rbCjX+LAn9DgclJDamtkpeGd8/jY3b/lKkPZvlN cFHvs4o/zpN35ruKk6VCpGiIoXrQjwuX9bH3ggCq1iUUGyF+f1FHacJdaFB/wukVonxH ZroOIU5K3icBK7EDmqk9kJ/1XJGwKrUD8b30pIYG5MPfHUFD+1D94aowNfu+P7IWpQAM /Sc/aUzcRCmPmOimQg0p8L7XRDp+2kohW8nkcyvqEScaoxxC1giG3yLvNIAy55HE/kTv XwjWE0lrchzet7YjPloGP6kxyjIlV4FxN28yTfxYdwxmBtejlhTu7m+C5PYnKNoB1K1E etHA== X-Gm-Message-State: ALoCoQm8yBjevZJxmG7uLhFc5LFLZ8lrdkvWq7C0zI5Eq/71Vvcr6kbBPJjKYqpbrB0hEBlDJNVm X-Received: by 10.140.94.175 with SMTP id g44mr34767155qge.2.1432165434100; Wed, 20 May 2015 16:43:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.250.72 with HTTP; Wed, 20 May 2015 16:43:33 -0700 (PDT) In-Reply-To: References: From: Mariangela Hills Date: Thu, 21 May 2015 05:13:33 +0530 Message-ID: Subject: Re: [Discuss] PCA - Log Event Publishing to BAM To: dev , Chamila De Alwis Cc: Imesh Gunaratne Content-Type: multipart/alternative; boundary=001a113ac046f594f705168bffaa --001a113ac046f594f705168bffaa Content-Type: text/plain; charset=UTF-8 Chamila, as we have the Python CA, I was under the impression that we are not going to support the Java Cartridge Agent from Stratos 4.1.0 onwards. Have I got the wrong picture? Regards, Mariangela *--* *Mariangela Hills* PMC Member & Committer of Apache Stratos Senior Technical Writer WSO2, Inc. lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com On Thu, May 21, 2015 at 5:09 AM, Mariangela Hills wrote: > Thanks, Chamila! I will update this wiki page. > > Regards, > Mariangela > > > > > *--* > *Mariangela Hills* > PMC Member & Committer of Apache Stratos > Senior Technical Writer > WSO2, Inc. > lean.enterprise.middleware. > m: +94 773 500185 > w: http://wso2.com > > > On Thu, May 21, 2015 at 2:06 AM, Rajkumar Rajaratnam > wrote: > >> 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 >> > > --001a113ac046f594f705168bffaa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Chamila, as we have the Python CA, I was under the impress= ion that we are not going to support the Java Cartridge Agent from Stratos = 4.1.0 onwards. Have I got the wrong picture?

Regards,
Mariangela

--

Mariangel= a Hills
PMC Member &am= p; Committer of Apache Stratos
Senior Technical Writer
<= /font>
WSO2, Inc.
lean.enterprise.middleware.=C2=A0


On Thu, May 21, 2015 at 5:09 AM, Mariangela = Hills <mariangela@wso2.com> wrote:
Thanks, Chamila! I will update this wiki pag= e.

=
Regards,<= br>Mariangela


--

Mariangela Hills
PMC Member & Committer of Apache Stratos
Senior Tec= hnical Writer
WSO2, Inc.
lean.enterpris= e.middleware.=C2=A0
m:=C2=A0+94 773 500185
w:=C2=A0<= /font>http://wso2.com


On Thu, May 21= , 2015 at 2:06 AM, Rajkumar Rajaratnam <rajkumarr@wso2.com>= wrote:
Thanks= for the info Chamila!
=
On Wed, May 20, 2015 at 7:19 PM, Chamila De = Alwis <chamilad@wso2.com> wrote:
Hi Raj,

Please find my commen= ts inline.

<= span>On Wed, May 20, 2015 at 6:57 PM, Rajkumar Rajaratnam <rajkumarr@wso2= .com> wrote:
<= div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-siz= e:small">Sorry I am not up-to-date with this feature.

1) Is this publishing PCA's logs to BAM or Cartridge's logs to BA= M?
The intention is to allow to publish s= ervice logs (eg: httpd.log), however any specified log file location will b= e scanned.
=C2=A0
2) Can it publish logs to more than one thrift receive= rs?
3) Can it publish logs to more than one thrift recei= vers in a load-balancing manner (1st event to 1st server and 2nd event to 2= nd server)?
4) Can it publish logs to more then one thri= ft receivers in a fail-over manner (if sending to 1st server fails, then tr= y to send it to 2nd server and so on)?
5) Is there any r= eceiver groups concept implemented? For example, publish events to CEP clus= ter 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 mechanis= m 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 i= mplemented, and there are no WSO2 Carbon DataBridge like event queuing in t= he Thrift publisher. The Java Cartridge Agent makes use of the WSO2 Carbon&= #39;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 b= e included, so
=C2=A0=C2=A0

If these are not impleme= nted yet, we will create a JIRA and track this for future release.
.. sounds good. :)



Regards,
Ch= amila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com





--
=
Rajkumar Rajaratna= m
Committer & PMC Member, Apache Stratos
=
Software Engineer, WSO2

Mobile : +94777568639
Blog : rajkumarr.com
<= /div>
<= /div>


--001a113ac046f594f705168bffaa--