[
https://issues.apache.org/jira/browse/EAGLE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070597#comment-15070597
]
ASF GitHub Bot commented on EAGLE-99:
-------------------------------------
Github user yonzhang commented on the pull request:
https://github.com/apache/incubator-eagle/pull/36#issuecomment-167044199
even after I re-open this PR, it still shows jenkins error
Thanks
Edward
From: anyway1021 <[email protected]<mailto:[email protected]>>
Reply-To: apache/incubator-eagle
<[email protected]<mailto:[email protected]>>
Date: Wednesday, December 23, 2015 at 18:01
To: apache/incubator-eagle
<[email protected]<mailto:[email protected]>>
Cc: "Zhang, Edward (GDI Hadoop)"
<[email protected]<mailto:[email protected]>>
Subject: Re: [incubator-eagle] EAGLE-99 policy distribution reporter (#36)
Edward, the apache ci was running on a problematic slave machine and gave
the wrong build status, which made the none-valued judgement on your pr. Do you
need to close and reopen this pr to re-fresh the status?
—
Reply to this email directly or view it on
GitHub<https://github.com/apache/incubator-eagle/pull/36#issuecomment-167023335>.
> policy distribution statistics to be printed in log
> ---------------------------------------------------
>
> Key: EAGLE-99
> URL: https://issues.apache.org/jira/browse/EAGLE-99
> Project: Eagle
> Issue Type: Improvement
> Affects Versions: 0.3.0
> Reporter: Edward Zhang
> Assignee: Edward Zhang
> Priority: Minor
> Fix For: 0.3.0
>
>
> Polices are distributed into different physical processes/threads, sometimes
> it is very hard to know which physical AlertExecutor handles which policies.
> Each time after Eagle framework polls policy changes, the framework will
> calculate policy distribution statistics and print that in log.
> This stats potentially can be reported into centralized eagle service for
> better visualization of the whole picture of policy distribution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
