eagle-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayesh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (EAGLE-481) Make alert engine topology to be one application so to be managed by Eagle API
Date Thu, 20 Jul 2017 17:53:05 GMT

     [ https://issues.apache.org/jira/browse/EAGLE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jayesh updated EAGLE-481:
-------------------------
    Fix Version/s:     (was: v0.5.0)
                   v0.5.1

> 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.1
>
>
> 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.4.14#64029)

Mime
View raw message