[ 
https://issues.apache.org/jira/browse/EAGLE-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643415#comment-15643415
 ] 

ASF GitHub Bot commented on EAGLE-741:
--------------------------------------

GitHub user garrettlish opened a pull request:

    https://github.com/apache/incubator-eagle/pull/613

    EAGLE-741: Make publishment settings both policy & stream awareness

    Currently our publishment is defined policy specific, we cannot publish the 
alert into different places for one policy although there are multiple output 
streams for this policy.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/garrettlish/incubator-eagle eagle741

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-eagle/pull/613.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 #613
    
----
commit 14d9bf133863514991594b044fd2507ad8c4810e
Author: Xiancheng Li <xiancheng...@ebay.com>
Date:   2016-11-07T05:55:20Z

    EAGLE-741: Make publishment settings both policy & stream awareness
    
    Currently our publishment is defined policy specific, we cannot publish the 
alert into different places for one policy although there are multiple output 
streams for this policy.

----


> Make publishment settings both policy & stream awareness
> --------------------------------------------------------
>
>                 Key: EAGLE-741
>                 URL: https://issues.apache.org/jira/browse/EAGLE-741
>             Project: Eagle
>          Issue Type: Improvement
>    Affects Versions: v0.5.0
>            Reporter: Garrett Li
>            Assignee: Garrett Li
>             Fix For: v0.5.0
>
>
> Currently our publishment is defined policy specific, we cannot publish the 
> alert into different places for one policy although there are multiple output 
> streams for this policy. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to