[
https://issues.apache.org/jira/browse/EAGLE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446600#comment-15446600
]
ASF GitHub Bot commented on EAGLE-481:
--------------------------------------
Github user yonzhang closed the pull request at:
https://github.com/apache/incubator-eagle/pull/392
> Make alert engine topology to be one application so to be managed by Eagle API
> ------------------------------------------------------------------------------
>
> Key: EAGLE-481
> URL: https://issues.apache.org/jira/browse/EAGLE-481
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: v0.5.0
> Reporter: Edward Zhang
> Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Eagle alert engine as of 0.5 is multiple separate storm topologies. Instead
> of running alert engine manually, we can leverage Eagle 0.5 application API
> to manage alert engine.
> Options:
> 1. Wrapper alert engine topology to be one Eagle application
> 2. Define a new service API to directly start/stop alert engine
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
