You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Oleg Nechiporenko (JIRA)" <ji...@apache.org> on 2016/01/15 11:36:39 UTC

[jira] [Updated] (AMBARI-14683) Add Filter in Alert instances table

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

Oleg Nechiporenko updated AMBARI-14683:
---------------------------------------
    Attachment: AMBARI-14683.patch

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