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

Hudson commented on AMBARI-14898:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4269 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4269/])
AMBARI-14898. Alerts: Ability to customize props and thresholds on 
(onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6d9e05995f6815a600021e0e84f3f29518989b36])
* ambari-web/test/mappers/alert_definitions_mapper_test.js
* ambari-web/app/styles/alerts.less
* ambari-web/app/views/main/alerts/definition_configs_view.js
* ambari-web/app/mappers/alert_definitions_mapper.js
* ambari-web/app/controllers/main/alerts/definition_configs_controller.js
* ambari-web/app/templates/main/alerts/configs/alert_config_parameter.hbs
* ambari-web/app/models/alerts/alert_definition.js
* ambari-web/test/controllers/main/alerts/definitions_configs_controller_test.js
* ambari-web/app/models/alerts/alert_config.js
* ambari-web/test/models/alerts/alert_config_test.js


> Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari 
> Web UI
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14898
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14898
>             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-14898.patch
>
>
> Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
> metrics Externalized. 
> The Usage screens relies on the alert_disk_space.py script to collect metrics 
> such as Disk utilization (percentage) and directory being checked. 
> The problem is that the directories being check in this script are: 
> 1. ROOT ("/") 
> 2. /usr/hdp 
> If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is 
> NOT OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag 
> applies to ROOT. 
> This would work on a OOTB standard cluster. However, many users, have 
> Partitions for the hadoop directories. In this instance, "/" is static, no 
> new content will be added. In this instance being at 80 or 90% is OK, this 
> directory will never grow beyond that. 
> "/usr/hdp" is a separate partition that grows in time. 
> Based on the above described check, the 80% of the root partition will 
> trigger a "CRITICAL" message, although the "/usr/hdp" partition is OK. 
> The selection of what directory is being checked should be EXTERNALIZED to a 
> configurable property to avoid these kinds of misleading messages. 
> CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
> triggers these) should be left up to the user, not hardcoded in the script. 
> This is a request to externalize the directories that should be checked, as 
> well as the Percentages into an external configurable property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to