[
https://issues.apache.org/jira/browse/EAGLE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-556:
---------------------------
Description:
Currently alert engine requires additional metadata like TopologyMeta, which in
fact could be automatically generated during starting alert engine.
*Changes*
* Add "ApplicationListener" in ApplicationProvider to support extensible
application lifecycle management callback listener
* Implement AlertUnitTopologyAppListener to add topology metadata when
topology is running and remove topology metadata when topology is stopped
was:Currently alert engine requires additional metadata like TopologyMeta,
which in fact could be automatically generated during starting alert engine.
> Install/Update Alert Topology Metadata when start alert engine
> --------------------------------------------------------------
>
> Key: EAGLE-556
> URL: https://issues.apache.org/jira/browse/EAGLE-556
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: v0.5.0
> Reporter: Hao Chen
> Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Currently alert engine requires additional metadata like TopologyMeta, which
> in fact could be automatically generated during starting alert engine.
> *Changes*
> * Add "ApplicationListener" in ApplicationProvider to support extensible
> application lifecycle management callback listener
> * Implement AlertUnitTopologyAppListener to add topology metadata when
> topology is running and remove topology metadata when topology is stopped
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)