Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Mon, 7 Mar 2016 13:19:40 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12947688.1457356760000.20364.1457356780719@Atlassian.JIRA>
In-Reply-To: <JIRA.12947688.1457356760000@Atlassian.JIRA>
References: <JIRA.12947688.1457356760000@Atlassian.JIRA>
 <JIRA.12947688.1457356760549@arcas>
Subject: [jira] [Created] (KARAF-4404) Create eventadmin collector
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Jean-Baptiste Onofr=C3=A9 created KARAF-4404:
-------------------------------------------

             Summary: 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 app=
ender:

{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 col=
lector which basically collects the events from framework/* and karaf/* top=
ics (or any topic that the user wants) and forward to the decanter/collect/=
* topics.

These approach have two advantages:
1. the user decides if he wants to enable the eventadmin collector by insta=
lling the decanter-collector-eventadmin feature (as the other collectors)
2. we don't change the collectors: they are still listening on decanter/col=
lect/* topics. So, we keep a key decanter feature: decouple data collection=
 for the appending.


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