| // |
| // Licensed under the Apache License, Version 2.0 (the "License"); |
| // you may not use this file except in compliance with the License. |
| // You may obtain a copy of the License at |
| // |
| // http://www.apache.org/licenses/LICENSE-2.0 |
| // |
| // Unless required by applicable law or agreed to in writing, software |
| // distributed under the License is distributed on an "AS IS" BASIS, |
| // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| // See the License for the specific language governing permissions and |
| // limitations under the License. |
| // |
| |
| === Architecture |
| |
| Apache Karaf Decanter uses OSGi EventAdmin to dispatch the harvested data between the collectors and the appenders, |
| and also to throw the alerts to the alerters: |
| |
| * `decanter/collect/*` EventAdmin topics are used by the collectors to send the harvested data. The appenders consume |
| from these topics and insert the data in a backend. |
| * `decanter/alert/*` EventAdmin topics are used by the checker to send the alerts. The alerters consume from |
| these topics. |
| |
| Decanter uses EventAdmin topics as monitoring events dispatcher. |
| |
| Collectors, appenders, and alerters are simple OSGi services exposed by different bundles. |
| |
| It means that you can easily extend Decanter adding your own collectors, appenders, or alerters. |
