[jira] [Created] (AMBARI-7258) Slider View: FE - Make ganglia monitoring optional when creating app

["Andrii Tkach (JIRA)" <ji...@apache.org>]

Andrii Tkach created AMBARI-7258:
------------------------------------

             Summary: Slider View: FE - Make ganglia monitoring optional when creating app
                 Key: AMBARI-7258
                 URL: https://issues.apache.org/jira/browse/AMBARI-7258
             Project: Ambari
          Issue Type: Task
          Components: ambari-web
    Affects Versions: 1.7.0
            Reporter: Andrii Tkach
            Assignee: Andrii Tkach
             Fix For: 1.7.0


When creating a Slider app via the wizard, in the Global configs section we currently have 3 Ganglia properties which always set Ganglia configs. We need to provide option to user whether he wants monitoring or not. 

We should add a _Enable Metrics_ checkbox in configs, which by default is unchecked (no metrics). When user proceeds, all 3 Ganglia configs are not set for the app, and hence, no metrics/graphs should be shown for the app.

If user checks that checkbox, then the 3 Ganglia configs show up. The 
{{ganglia_server_id}} config should be a drop-down, and {{ganglia_server_port}} should be a read-only config. 

The drop-down should get its values from {{ganglia_custom_clusters}} config of {{ganglia-env}} of Ambari-server.  {{ganglia_custom_clusters}}  config will have CSV like below in pairs - {code}"name1","port1","name2","port2",...{code}
{code}
"HBaseCluster1","7000","AccumuloCluster1", "7001","HBaseCluster2","7002"
{code}

The drop-down will show all the _ganglia_clusters_, and as user changes selection, it will update the {{ganglia_server_port}} config value. User should not directly change {{ganglia_server_port}}, only by selecting a cluster in the combo-box.

If user enables the checkbox and creates app, then metric graphs should be shown for that app. Whether metric graphs are shown or not depends on {{ganglia_server_host}} config being available for that app.



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