[
https://issues.apache.org/jira/browse/AMBARI-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123435#comment-15123435
]
Hudson commented on AMBARI-14683:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.2 #267 (See
[https://builds.apache.org/job/Ambari-branch-2.2/267/])
AMBARI-14683 .Add Filter in Alert instances table (onechiporenko)
(onechiporenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=492d47278cb1242d061bff39655add67dc4bdfe4])
* ambari-web/app/views/main/alert_definitions_view.js
* ambari-web/app/views/common/filter_view.js
* ambari-web/app/views/main/alerts/definition_details_view.js
* ambari-web/test/views/common/filter_view_test.js
* ambari-web/app/templates/main/alerts/definition_details.hbs
* ambari-web/app/styles/alerts.less
> 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)
