From general-return-2083-apmail-logging-general-archive=logging.apache.org@logging.apache.org Sun Oct 6 21:03:46 2013
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 8552010E6A
for ; Sun, 6 Oct 2013 21:03:46 +0000 (UTC)
Received: (qmail 91529 invoked by uid 500); 6 Oct 2013 21:03:44 -0000
Delivered-To: apmail-logging-general-archive@logging.apache.org
Received: (qmail 91457 invoked by uid 500); 6 Oct 2013 21:03:38 -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 91447 invoked by uid 99); 6 Oct 2013 21:03:37 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Oct 2013 21:03:37 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of grobmeier@gmail.com designates 209.85.215.180 as permitted sender)
Received: from [209.85.215.180] (HELO mail-ea0-f180.google.com) (209.85.215.180)
by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Oct 2013 21:03:31 +0000
Received: by mail-ea0-f180.google.com with SMTP id h10so2786800eaj.39
for ; Sun, 06 Oct 2013 14:03:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=from:to:cc:subject:date:message-id:mime-version:content-type;
bh=F503DhjvGXIL/EmUo6VJxSYN7PNpVVD5psNzw8tEn2Q=;
b=zMyushmwmjdZNX52Sd6GWGLBzyl0Ry7+q7RRqVOW6TbKwKmNbxF35mH5U7y7Ao9j1B
B1yUJh5XIilgIZIMixMiC0qmemEO2gGF3Xt75vinLK+XYErdBHYVq2w4GuxftMEb4z7F
0lNCym6PVz/T4N38du6RNkNb5ExhJpTKYfi35+wPnBvWC+uqC7IrqSYRyNGmOanUbVQ6
zlLhxiZVA//gTVaXaYyIFf3FFFJU4tgLMvCOOmNLSH9ygYxxilZWwKOVo9jd5m69AOGP
mtdQxVFVrBhrKzcZ6hJqdSiM0sHC4MqsPQe9u9ZfaL7DmKJ+JNC5Ham+9uUbmzjgGHfS
ZN1Q==
X-Received: by 10.14.88.65 with SMTP id z41mr42684558eee.38.1381093390736;
Sun, 06 Oct 2013 14:03:10 -0700 (PDT)
Received: from [192.168.56.1] (p57B07F7F.dip0.t-ipconnect.de. [87.176.127.127])
by mx.google.com with ESMTPSA id r48sm55110077eev.14.1969.12.31.16.00.00
(version=TLSv1 cipher=RC4-SHA bits=128/128);
Sun, 06 Oct 2013 14:03:10 -0700 (PDT)
From: "Christian Grobmeier"
To: "Logging General"
Cc: "Benedikt Ritter"
Subject: Introducing Lionbeast
Date: Sun, 06 Oct 2013 23:03:08 +0200
Message-ID: <442211F9-B286-4670-8D6A-2C4612D8CEF6@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate Trial (1.6r3738)
X-Virus-Checked: Checked by ClamAV on apache.org
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