[
https://issues.apache.org/jira/browse/AMBARI-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173318#comment-14173318
]
Yusaku Sako commented on AMBARI-7808:
-------------------------------------
[~jaoki]
This JIRA is not intended for generically migrating all hard-coded configs in
Ambari Web to the stack definition (though we should have a separate JIRA for
that).
The scope of this particular JIRA should be to move service metrics graph
metadata that is hard-coded in Ambari Web to the stack definition. I.e., we
should remove service_graph_config.js created in AMBARI-7601 and make it part
of the stack definition.
In addition, I think we should think about how we could represent service
graphs in the stack definition so that we can remove App.ChartServiceMetrics*
classes in Ambari Web (see
ambari-web/app/views/main/service/info/metrics/<service-name>). This way, we
can easily define new graphs for new/existing services by editing the stack
definition and not Ambari Web code.
> Service pluggability: metrics graphs to show in Ambari Web's service pages
> should be declared in the stack definition
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-7808
> URL: https://issues.apache.org/jira/browse/AMBARI-7808
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-web, stacks
> Affects Versions: 1.7.0
> Reporter: Yusaku Sako
> Fix For: 2.0.0
>
>
> Currently, which metrics graphs to display in Ambari Web's service pages is
> hardcoded in ambari-web code.
> We should make it such that 1) the graphs to display are declared in the
> stack definition for each service and 2) ambari-web code needs to load this
> information and display appropriate graphs under the service page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
