[jira] [Updated] (AMBARI-6908) Alerts: AlertDefinition Should Have a Label

["Jonathan Hurley (JIRA)" <ji...@apache.org>]

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

Jonathan Hurley updated AMBARI-6908:
------------------------------------

    Summary: Alerts: AlertDefinition Should Have a Label  (was: Alerts: AlertDefinition Should Have a Description)

> Alerts: AlertDefinition Should Have a Label
> -------------------------------------------
>
>                 Key: AMBARI-6908
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6908
>             Project: Ambari
>          Issue Type: Task
>    Affects Versions: 1.7.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 1.7.0
>
>
> The design documentation (and JSON so far) has a label field for every AlertDefinition. This label field is really a description of the AlertDefinition. It's a human readable field that properly identifies the AlertDefintiion but is not unique (like the name).
> Example:
> {code}
>  "NAMENODE": [
>     {
>       "name": "hdfs_capacity_check", // unique name
>       "label": "HDFS Capacity Utilization",
> ...
> {code}
> Since this is a DDL change, it's desirable to have this in 1.7.0 since that's where the alert database model first appears (and prevents the need to write an upgrade for this field).



--
This message was sent by Atlassian JIRA
(v6.2#6252)