eagle-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Garrett Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (EAGLE-947) Publishers with same policy but different schema could produce duplicate alerts
Date Fri, 10 Mar 2017 03:49:37 GMT

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

Garrett Li updated EAGLE-947:
-----------------------------
    Summary: Publishers with same policy but different schema could produce duplicate alerts
 (was: Publishers with different schema could produce duplicate alerts)

> Publishers with same policy but different schema could produce duplicate alerts
> -------------------------------------------------------------------------------
>
>                 Key: EAGLE-947
>                 URL: https://issues.apache.org/jira/browse/EAGLE-947
>             Project: Eagle
>          Issue Type: Bug
>          Components: Core::Alert Engine
>    Affects Versions: v0.5.0
>            Reporter: Garrett Li
>            Assignee: Garrett Li
>             Fix For: v0.5.0
>
>
> Assume that we have policy1 which have 2 kinds of output streams, one is stream1 and
another is stream2. If publisher1 is configured for policy1 and stream1, and publisher2 is
configured for policy1 and stream2, current code will produce 2 alerts for either stream1
or stream2. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message