Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 29 Jan 2016 10:14:39 +0000 (UTC)
From: "Oleg Nechiporenko (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12931420.1452853935000.247981.1454062479798@Atlassian.JIRA>
In-Reply-To: <JIRA.12931420.1452853935000@Atlassian.JIRA>
References: <JIRA.12931420.1452853935000@Atlassian.JIRA>
 <JIRA.12931420.1452853935562@arcas>
Subject: [jira] [Reopened] (AMBARI-14683) Add Filter in Alert instances
 table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Nechiporenko reopened AMBARI-14683:
----------------------------------------

> 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)