ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14683) Add Filter in Alert instances table
Date Fri, 15 Jan 2016 11:15:39 GMT

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

Hadoop QA commented on AMBARI-14683:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12782503/AMBARI-14683.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 2 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-web.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/4931//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4931//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
>
>
> 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)

Mime
View raw message