[
https://issues.apache.org/jira/browse/EAGLE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438456#comment-15438456
]
ASF GitHub Bot commented on EAGLE-481:
--------------------------------------
GitHub user yonzhang opened a pull request:
https://github.com/apache/incubator-eagle/pull/392
hdfs audit log + alert engine end-2-end
https://issues.apache.org/jira/browse/EAGLE-481
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yonzhang/incubator-eagle develop
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/392.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #392
----
commit 9efa8cc13959d5be552cf8a08cbdde874ba25b7d
Author: yonzhang <[email protected]>
Date: 2016-08-26T04:37:33Z
hdfs audit log + alert engine end-2-end
----
> 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)
