[
https://issues.apache.org/jira/browse/EAGLE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070619#comment-15070619
]
ASF GitHub Bot commented on EAGLE-99:
-------------------------------------
Github user anyway1021 commented on the pull request:
https://github.com/apache/incubator-eagle/pull/36#issuecomment-167047807
This is tricky. I also tested my pr for testing, and the result is, if the
CI job enables pr trigger, any failure can cause your pr to be marked as Fail;
and if I disable the trigger, your pr cannot be refreshed.
In this situation, while I'm doing experiment to setup the job, the CI job
may bring impact to normal pr. I should have configured it to other git repo
than eagle to avoid such things happen, but any github repo out of apache org
is ignored by the pr builder plugin on that Jenkins server.
So, as a whole, let me turn the job's configuration to make it succeed
every time and you please reopen your pr to refresh the status, so that your
process won't be blocked. Make sense?
> 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)
