[
https://issues.apache.org/jira/browse/AMBARI-8237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203954#comment-14203954
]
Hadoop QA commented on AMBARI-8237:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12680482/AMBARI-8237.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/576//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/576//console
This message is automatically generated.
> Alerts: Provide Summary Structure On Alerts Endpoint
> ----------------------------------------------------
>
> Key: AMBARI-8237
> URL: https://issues.apache.org/jira/browse/AMBARI-8237
> Project: Ambari
> Issue Type: Task
> Components: alerts, ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-8237.patch
>
>
> In the alert definitions summary page we show all the definitions along with
> counts of how many are OK, WARN, ERROR, etc. We need the alert instance
> counts rolled up into the alert definition response on cluster. This will
> save UI from getting all instances and then determining counts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
