You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2015/02/04 21:03:35 UTC
[jira] [Updated] (AMBARI-9479) Alerts: UI should validate threshold
values for PORT and METRIC type alerts
[ https://issues.apache.org/jira/browse/AMBARI-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srimanth Gunturi updated AMBARI-9479:
-------------------------------------
Attachment: AMBARI-9479.patch
Tests pass and has been verified on live cluster.
{noformat}
[exec]
[exec] 5311 tests complete (8 seconds)
[exec] 63 tests pending
[exec]
{noformat}
> Alerts: UI should validate threshold values for PORT and METRIC type alerts
> ---------------------------------------------------------------------------
>
> Key: AMBARI-9479
> URL: https://issues.apache.org/jira/browse/AMBARI-9479
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 2.0.0
>
> Attachments: AMBARI-9479.patch
>
>
> Ability to save wrong Tresholds time in alerts so alerts UI needs to enforce checking for PORT and METRIC type alerts.
> For type=PORT alerts, thresholds should be integer > 0.
> For type=METRIC alerts, this can vary depending on the metric, therefore, thresholds should enforce "numeric" values.
> STR:
> 1. Login to Ambari, go to Alerts tab
> 2. Click on alert
> 3. Click Edit in Configuration window
> 4. Enter wrong time/message for tresholds
> ER: error message/Save button not enabled
> AR: no error message, ability to click Save
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)