[
https://issues.apache.org/jira/browse/AMBARI-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123426#comment-15123426
]
Hadoop QA commented on AMBARI-14683:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12785143/AMBARI-14683_branch-2.2.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5113//console
This message is automatically generated.
> Add Filter in Alert instances table
> -----------------------------------
>
> Key: AMBARI-14683
> URL: https://issues.apache.org/jira/browse/AMBARI-14683
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14683.patch, AMBARI-14683_branch-2.2.patch
>
>
> While troubleshooting big cluster deployments, I've found it really difficult
> to find CRIT and WARN alerts for a specific alert definition, because there's
> no filter in the alert instance table.
> The table can display up to 100, but you cannot sort or filter by "Status",
> and the default sort order is host name, so you have to page thru many times
> to find alerts of a certain status.
> We should at the very least add filtering by Status.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
