Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Wed, 23 Mar 2016 13:08:25 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12947688.1457356760000.29216.1458738505471@Atlassian.JIRA>
In-Reply-To: <JIRA.12947688.1457356760000@Atlassian.JIRA>
References: <JIRA.12947688.1457356760000@Atlassian.JIRA>
 <JIRA.12947688.1457356760549@arcas>
Subject: [jira] [Commented] (KARAF-4404) Create eventadmin collector
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-4404?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1520=
8375#comment-15208375 ]=20

ASF subversion and git services commented on KARAF-4404:
--------------------------------------------------------

Commit f0fb00d4e0719b514a3375279bee3cb1747f932f in karaf-decanter's branch =
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=3Dkaraf-decanter.git;h=3Df0fb00=
d ]

KARAF-4404 - Document the eventadmin collector


> Create eventadmin collector
> ---------------------------
>
>                 Key: KARAF-4404
>                 URL: https://issues.apache.org/jira/browse/KARAF-4404
>             Project: Karaf
>          Issue Type: New Feature
>          Components: decanter
>            Reporter: Jean-Baptiste Onofr=C3=A9
>            Assignee: Jean-Baptiste Onofr=C3=A9
>             Fix For: decanter-1.1.0
>
>
> Right now, we catch the eventadmin events directly on the elasticsearch a=
ppender:
> {code}
> @Component(
>      name =3D "org.apache.karaf.decanter.appender.elasticsearch",
>      immediate =3D true,
>      property =3D {"event.topics=3Ddecanter/collect/*",
>                  "event.topics=3Dorg/osgi/framework/*",
>                  "event.topics=3Dorg/apache/karaf/*"
>                  }
> {code}
> It couples the events harvesting (eventadmin) from the appender.
> A better approach would be to introduce a decanter-collector-eventadmin c=
ollector which basically collects the events from framework/* and karaf/* t=
opics (or any topic that the user wants) and forward to the decanter/collec=
t/* topics.
> These approach have two advantages:
> 1. the user decides if he wants to enable the eventadmin collector by ins=
talling the decanter-collector-eventadmin feature (as the other collectors)
> 2. we don't change the collectors: they are still listening on decanter/c=
ollect/* topics. So, we keep a key decanter feature: decouple data collecti=
on for the appending.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)