Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 3 Dec 2014 13:05:12 +0000 (UTC)
From: "Aleksandr Kovalenko (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12759163.1417611775000.67807.1417611912313@Atlassian.JIRA>
In-Reply-To: <JIRA.12759163.1417611775000@Atlassian.JIRA>
References: <JIRA.12759163.1417611775000@Atlassian.JIRA>
 <JIRA.12759163.1417611775688@arcas>
Subject: [jira] [Updated] (AMBARI-8520) Alerts UI: In create alert wizard,
 need per alert-type configurations on Page-2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksandr Kovalenko updated AMBARI-8520:
----------------------------------------
    Attachment: AMBARI-8520.patch

> Alerts UI: In create alert wizard, need per alert-type configurations on Page-2
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-8520
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8520
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8520.patch
>
>
> On the create alert wizard we have 3 pages. The first page selects an alert-type. The second page configures that alert-type. The third page reviews and makes the POST call.
> In this JIRA we need to provide the configuration content per alert-type. This should include configuring the 5 different alert-types.
> We need to keep in mind that alert-definitions can be created for services, and for hosts. So the UI should look like this
> {noformat}
>  o[radio button] Service Alert Definition
>  	Service: [combo for picking service]
>  	Component: [combo for picking component]
>  	Scope: [combo for Any|Service|Host]
>  o[radio button] Host Alert Definition
> {noformat}
> {{Service Alert Definition}} is selected by default. 
> Selecting {{Host Alert Definition}} disables the above 3 combos. However, in the API, it fills following values
> {code}
>      "AlertDefinition" : {
>         ...
>         "cluster_name" : "c1",
>         "component_name" : "AMBARI_AGENT",
>         "scope" : "HOST",
>         "service_name" : "AMBARI",
>         ...
>       }
> {code}


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