| Summary: | [RFE] Dashboard - provide drilldown for utilization | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine-dashboard | Reporter: | manikkandanb | ||||
| Component: | General | Assignee: | Vojtech Szocs <vszocs> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Pavel Novotny <pnovotny> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | unspecified | CC: | bugs, manikkandanb, mgoldboi, oourfali | ||||
| Target Milestone: | --- | Keywords: | FutureFeature | ||||
| Target Release: | --- | Flags: | oourfali:
ovirt-future?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-05-15 12:04:42 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
manikkandanb
2016-12-12 15:25:24 UTC
That was by design. Moran - any thoughts on that? I think that the source of the confusion is on the purpose of the top utilized resources widget. the intention wasn't to provide a drilldown capability for utilization (which is available to some level, using the cluster utilization widget) but to quickly pop up the possible bottlenecks on the system or the objects which needs attention. if a host is running with high level of mem - it will swap, or if a vm is running with high utilization of memory - it may need some mem addition. does it make any sense? Hi Moran, Thank you for detailing the intent behind the current design. However, it doesn't make sense to me, since I am already biased in expecting a drill down when the pie chart responded to a click and opened a bar chart. If this is as per design, could this bug be treated as a feature request, since that would also serve the purpose of identifying bottlenecks. There are no plans to extend the dashboard at the moment. Closing as wontfix. |