[
https://issues.apache.org/jira/browse/CLOUDSTACK-9783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885615#comment-15885615
]
ASF GitHub Bot commented on CLOUDSTACK-9783:
--------------------------------------------
Github user rashmidixit commented on the issue:
https://github.com/apache/cloudstack/pull/1944
@rhtyd On the contrary, I think you adding metrics as pluggable API is a
good idea. However, to seriously make the feature pluggable the UI component
should also load based on a plugin based flag.
For example (I am not sure if the current design makes this possible), the
plugin should return a flag in the listCapabilities API which tells the UI that
metrics is enabled. If this flag is present, the metrics button should appear,
else not.
> Improve metrics view performance
> --------------------------------
>
> Key: CLOUDSTACK-9783
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9783
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: Future, 4.10.0.0, 4.9.3.0
>
>
> Metrics view is a pure frontend feature, where several API calls are made to
> generate the metrics view tabular data. In very large environments, rendering
> of these tables can take a lot of time, especially when there is high
> latency. The improvement task is to reimplement this feature by moving the
> logic to backend so metrics calculations happen at the backend and final
> result can be served by a single API request.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
