[
https://issues.apache.org/jira/browse/AMBARI-8520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233014#comment-14233014
]
Hudson commented on AMBARI-8520:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit-docker #368 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/368/])
AMBARI-8520. Alerts UI: In create alert wizard, need per alert-type
configurations on Page-2. (akovalenko) (akovalenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ff1459b88ce23298f5a705fc9e6c091fb30344e3)
*
ambari-web/app/controllers/main/alerts/add_alert_definition/step1_controller.js
* ambari-web/app/templates/main/alerts/configs.hbs
* ambari-web/test/controllers/main/alerts/definitions_configs_controller_test.js
* ambari-web/app/views/main/alerts/definition_configs_view.js
* ambari-web/app/models/alert_config.js
*
ambari-web/app/controllers/main/alerts/add_alert_definition/step2_controller.js
* ambari-web/app/templates/main/alerts/definition_details.hbs
* ambari-web/app/controllers/main/alerts/definition_configs_controller.js
* ambari-web/app/styles/alerts.less
*
ambari-web/app/controllers/main/alerts/add_alert_definition/step3_controller.js
* ambari-web/app/templates/main/alerts/add_alert_definition/step2.hbs
* ambari-web/app/routes/add_alert_definition_routes.js
> 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)
