3. What is the nature and description of the request? The customer would like the ability to monitor the RHEV-M server's stats/vitals in a rhevm-reports report. 4. Why does the customer need this? (List the business requirements here) This would allow them to see the health of the manager over a long period of time. 5. How would the customer like to achieve this? (List the functional requirements here) Additional report(s) in Jasper to view RHEV-M cpu usage, memory usage, and network utilization among others. 10. List any affected packages or components. ovirt-engine-backend ovirt-engine-reports 11. Would the customer be able to assist in testing this functionality if implemented? Yes
Currently engine does not collect any host level information (as required by the report definition above). We need first to collect this data, and than can those reports be generated.
Removing support for reports in 4.0. Will reopen if relevant.
Still relevant. Reopening to track addition to metrics store.
*** Bug 1113772 has been marked as a duplicate of this bug. ***
Customer has also requested the inclusion of Engine-Level reports within RHEV to provide insight into key aspects of environment configuration. The two reports that were explicitly mentioned were Memory Heap I/O and Database I/O.
Shirly, can you provide devel-ack for 4.2?
These statistics should be provided in the metrics store. User can create ad hoc reports and dashboards using kibana.
should this be cloned upstream?
Opened upstream bug 1475113
tested in ovirt-engine-metrics-1.1.1-0.3.beta2.20171114114644.el7ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1486
BZ<2>Jira Resync