Return-Path: X-Original-To: apmail-logging-general-archive@www.apache.org Delivered-To: apmail-logging-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A53D910963 for ; Fri, 25 Oct 2013 08:14:29 +0000 (UTC) Received: (qmail 19019 invoked by uid 500); 25 Oct 2013 08:14:29 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 18864 invoked by uid 500); 25 Oct 2013 08:14:21 -0000 Mailing-List: contact general-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Logging General" List-Id: Delivered-To: mailing list general@logging.apache.org Received: (qmail 18854 invoked by uid 99); 25 Oct 2013 08:14:19 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2013 08:14:19 +0000 Received: from localhost (HELO mail-we0-f175.google.com) (127.0.0.1) (smtp-auth username britter, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2013 08:14:18 +0000 Received: by mail-we0-f175.google.com with SMTP id t61so3410956wes.20 for ; Fri, 25 Oct 2013 01:14:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ZRlzVoLpEWsgLN2AwiA179ZB+fDs7sTzADx4UwPb+Mg=; b=biU69U+30nnmSbD5S4fxxnaVpX4CM3Koj99hX/UbM6PP4GIDt4YtYntBquBMwIpiB5 5fXDIPR5CL+mJcmE+x6kJiSZLUHUF9EiMOUxhLLmnWr+YWc46xkbFkWrfXr5a2lt2pWG Vv3QCtF0lms6nhWWgSNR4EBBjGQiRSwE2t64FyEH6lzahDtEp0BMjhPs5ZDGlmCcmFSY AleHKIqf8kmTlaoHSxvAdnONnmaQZiEzyraU0t0eOpajlNu67MTrnjl14zLlM2s78Nmu hjl2pk75gJyD4zBX2RfnxLr44USv6HMY53Y8v7CX6AX/Yca9vBDop8PGyXdAIoAdBb3V HMGQ== MIME-Version: 1.0 X-Received: by 10.194.47.236 with SMTP id g12mr15169wjn.92.1382688856787; Fri, 25 Oct 2013 01:14:16 -0700 (PDT) Received: by 10.194.190.136 with HTTP; Fri, 25 Oct 2013 01:14:16 -0700 (PDT) In-Reply-To: References: <442211F9-B286-4670-8D6A-2C4612D8CEF6@gmail.com> Date: Fri, 25 Oct 2013 10:14:16 +0200 Message-ID: Subject: Re: Introducing Lionbeast From: Benedikt Ritter To: Logging General Content-Type: multipart/alternative; boundary=047d7b86d37624d4dd04e98c56cf --047d7b86d37624d4dd04e98c56cf Content-Type: text/plain; charset=ISO-8859-1 Hey guys, what about this. When do we get started? :-) I've seen that there have been some issues about the log4j-extras release. Is there anything I can do to get it out of the door? Regards, Benedikt 2013/10/7 Benedikt Ritter > Hello, > > Christian, thanks for the introduction :-) I've had a very short look at > trunk of the extras package. It's some work to do to get this stuff up to > date, so we better start right away ;-) Just point me to the repository > after you have decided where to host the development. > > Best regards, > Benedikt > > > 2013/10/7 Scott Deboy > >> Sounds great! I definitely would like to help on the log4j2 receivers >> portion and any syncing you want to do with Chainsaw. >> >> >> Scott >> >> >> On 10/6/13, Christian Grobmeier wrote: >> > Hello folks! >> > >> > early this year I wrote a small and simply http server for demonstration >> > purposes. It's based on NIO. When I picked up this task I always thought >> > it would be good for an idea I have on logging for a while now. >> > >> > Here it is: >> > https://bitbucket.org/grobmeier/lionbeast >> > >> > I would like to change the server in a way so it can make use of Log4j >> > receivers to receive logging events. Lionbeast shall provide a way to >> > manipulate these events and enable to create some metrics or something >> > similar. At the moment it is possible to create dynamic websites using >> > JRuby. I would like to have "Loglets" one day. This is basically a >> > script or implemented class which lets users work with the events the >> > way they want. >> > >> > I absolutely know about Apache Flume. I consider Flume the "big brother" >> > of Lionbeast. Lionbeast aims to be easy to use, install and extend. I >> > consider it more to be a partner of Chainsaw actually. Like the >> > server-side Version of Chainsaw. Actually I believe there might be some >> > opportunities if Chainsaw and Lionbeast would come together. >> > >> > If you like my idea, I would like to contribute the current code and ask >> > for a Git-Repository at Infra. >> > My current plan is to work on it over years change mostly and thats why >> > I am starting now to have it ready for that time. >> > In addition I would like to put some work in the current Receivers. I >> > don't know if they currently work with Log4j2 but I guess not so well. I >> > think there should be a receivers package directly in the Log4j 2 trunk, >> > maybe even in the core. >> > >> > I recently spoke to Benedikt Ritter who is a committer/PMC at Apache >> > Commons. I told him about my ideas and he motivated me to move forward >> > with it. Furthermore Benedikt expressed his interest to participate. I >> > would like to give him access to the Git repository as well. We should >> > also discuss if we should open a sandbox for logging in general, where >> > interested fellow committers can contribute code without having >> > committer-ship at logging. >> > >> > Thoughts? Comments? Likes? Dislikes? >> > >> > Cheers >> > Christian >> > >> > >> > --- >> > http://www.grobmeier.de >> > @grobmeier >> > GPG: 0xA5CC90DB >> > >> > > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter --047d7b86d37624d4dd04e98c56cf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hey guys,

what about this. When do we g= et started? :-) I've seen that there have been some issues about the lo= g4j-extras release. Is there anything I can do to get it out of the door?

Regards,
Benedikt


2013/10/7 Benedikt Ritter <= britter@apache.org>
Hello,

C= hristian, thanks for the introduction :-) I've had a very short look at= trunk of the extras package. It's some work to do to get this stuff up= to date, so we better start right away ;-) Just point me to the repository= after you have decided where to host the development.

Best regards,
Benedikt


2013/10/7 Scott Deboy <scott.deboy@gmail.com><= /span>
Sounds great! =A0I definitely would like to = help on the log4j2 receivers
portion and any syncing you want to do with Chainsaw.


Scott


On 10/6/13, Christian Grobmeier <grobmeier@gmail.com> wrote:
> Hello folks!
>
> early this year I wrote a small and simply http server for demonstrati= on
> purposes. It's based on NIO. When I picked up this task I always t= hought
> it would be good for an idea I have on logging for a while now.
>
> Here it is:
> https://bitbucket.org/grobmeier/lionbeast
>
> I would like to change the server in a way so it can make use of Log4j=
> receivers to receive logging events. Lionbeast shall provide a way to<= br> > manipulate these events and enable to create some metrics or something=
> similar. At the moment it is possible to create dynamic websites using=
> JRuby. I would like to have "Loglets" one day. This is basic= ally a
> script or implemented class which lets users work with the events the<= br> > way they want.
>
> I absolutely know about Apache Flume. I consider Flume the "big b= rother"
> of Lionbeast. Lionbeast aims to be easy to use, install and extend. I<= br> > consider it more to be a partner of Chainsaw actually. Like the
> server-side Version of Chainsaw. Actually I believe there might be som= e
> opportunities if Chainsaw and Lionbeast would come together.
>
> If you like my idea, I would like to contribute the current code and a= sk
> for a Git-Repository at Infra.
> My current plan is to work on it over years change mostly and thats wh= y
> I am starting now to have it ready for that time.
> In addition I would like to put some work in the current Receivers. I<= br> > don't know if they currently work with Log4j2 but I guess not so w= ell. I
> think there should be a receivers package directly in the Log4j 2 trun= k,
> maybe even in the core.
>
> I recently spoke to Benedikt Ritter who is a committer/PMC at Apache > Commons. I told him about my ideas and he motivated me to move forward=
> with it. Furthermore Benedikt expressed his interest to participate. I=
> would like to give him access to the Git repository as well. We should=
> also discuss if we should open a sandbox for logging in general, where=
> interested fellow committers can contribute code without having
> committer-ship at logging.
>
> Thoughts? Comments? Likes? Dislikes?
>
> Cheers
> Christian
>
>
> ---
> http://www.grobm= eier.de
> @grobmeier
> GPG: 0xA5CC90DB
>



<= /div>
--



-- --047d7b86d37624d4dd04e98c56cf--