Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 3 Feb 2016 14:03:39 +0000 (UTC)
From: "Oleg Nechiporenko (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12936336.1454507901000.288705.1454508219843@Atlassian.JIRA>
In-Reply-To: <JIRA.12936336.1454507901000@Atlassian.JIRA>
References: <JIRA.12936336.1454507901000@Atlassian.JIRA>
 <JIRA.12936336.1454507901862@arcas>
Subject: [jira] [Commented] (AMBARI-14898) Alerts: Ability to customize
 props and thresholds on SCRIPT alerts via Ambari Web UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Oleg Nechiporenko commented on AMBARI-14898:
--------------------------------------------

  24136 tests complete (19 seconds)
  156 tests pending

> 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: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>             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)