[
https://issues.apache.org/jira/browse/EAGLE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-302.
-------------------------------
Resolution: Not A Problem
in v0.5, the alert engine is redesign and the topo-mgmt is removed.
> Add sample main app that read config for alert-executor to make onboard
> easier with topo-mgmt
> ---------------------------------------------------------------------------------------------
>
> Key: EAGLE-302
> URL: https://issues.apache.org/jira/browse/EAGLE-302
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: v0.4.0
> Reporter: Su Ralph
> Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Currently, if user have a simple request of do some alerting where the data
> source is well matched json to stream schema definition.
> He has to write a code like KafkaStreamMonitorApp, specify the alert executor
> id, like what we do for HadoopJmxMetricMonitor.
> This steps are good before v0.4, since at that time user need to manually
> start the topology. In v0.4, we have topo-mgmt, which we could encourage user
> to start/stop topology remotely through api/ui. We could provide/enhance to
> provide an sample app that consume for one policy executor id(from the
> config). So that for typical use case, user only need to specify the
> application.conf, then a topology with alert function could be started though
> UI without any code/jar submit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
