You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/02/12 11:07:18 UTC
[jira] [Commented] (KARAF-4321) Add log4j socket collector
[ https://issues.apache.org/jira/browse/KARAF-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144347#comment-15144347 ]
ASF subversion and git services commented on KARAF-4321:
--------------------------------------------------------
Commit 74f8f8c83a33e38f422396744dcd343f22c681f6 in karaf-decanter's branch refs/heads/master from [~chris@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=74f8f8c ]
[KARAF-4321] Add log4j socket collector
> Add log4j socket collector
> --------------------------
>
> Key: KARAF-4321
> URL: https://issues.apache.org/jira/browse/KARAF-4321
> Project: Karaf
> Issue Type: New Feature
> Components: decanter
> Affects Versions: decanter-1.0.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: decanter-1.0.2
>
>
> One use case for decanter is to run it as a kind of logging aggregator for a machine.
> You start up one instance of karaf with decanter and let it collect logging informations for all other processes on the machine.
> So we need a slim mechanism to transport logging informations from OSGi and non OSGi processes to decanter.
> The og4j socket appender seems like a good candidate. So we should have a decanter collector that listens for log4j messages on a socket.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)