karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Created] (KARAF-4404) Create eventadmin collector
Date Mon, 07 Mar 2016 13:19:40 GMT
Jean-Baptiste Onofré 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é
            Assignee: Jean-Baptiste Onofré
             Fix For: decanter-1.1.0


Right now, we catch the eventadmin events directly on the elasticsearch appender:

{code}
@Component(
     name = "org.apache.karaf.decanter.appender.elasticsearch",
     immediate = true,
     property = {"event.topics=decanter/collect/*",
                 "event.topics=org/osgi/framework/*",
                 "event.topics=org/apache/karaf/*"
                 }
{code}

It couples the events harvesting (eventadmin) from the appender.

A better approach would be to introduce a decanter-collector-eventadmin collector which basically
collects the events from framework/* and karaf/* topics (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 installing the decanter-collector-eventadmin
feature (as the other collectors)
2. we don't change the collectors: they are still listening on decanter/collect/* 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)

Mime
View raw message