[
https://issues.apache.org/jira/browse/EAGLE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Su Ralph updated EAGLE-519:
---------------------------
Description:
1. no data for an entire stream won't trigger gap alert (use local time & batch
window)
2. no data policies definition is too complex, make the nodata offer optional
settings in stream definition
3. bolt parallellism will cause multiple alerts in the same time window (use
loopback)
The extension of no data alert design is posted at
https://cwiki.apache.org/confluence/display/EAG/Alert+Engine+Extension.
was:
1. no data for an entire stream won't trigger gap alert (use local time & batch
window)
2. no data policies definition is too complex, make the nodata offer optional
settings in stream definition
3. bolt parallellism will cause multiple alerts in the same time window (use
loopback)
> No data / gap alert enhancement
> -------------------------------
>
> Key: EAGLE-519
> URL: https://issues.apache.org/jira/browse/EAGLE-519
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: v0.5.0
> Reporter: Garrett Li
> Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> 1. no data for an entire stream won't trigger gap alert (use local time &
> batch window)
> 2. no data policies definition is too complex, make the nodata offer optional
> settings in stream definition
> 3. bolt parallellism will cause multiple alerts in the same time window (use
> loopback)
> The extension of no data alert design is posted at
> https://cwiki.apache.org/confluence/display/EAG/Alert+Engine+Extension.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
