Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 950813

Summary:	[RFE] Metrics should include information about the RHV-M server (CPU, memory, network, etc.)
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Bryan Yount <byount>
Component:	ovirt-engine-metrics	Assignee:	Shirly Radco <sradco>
Status:	CLOSED ERRATA	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.1.2	CC:	bsettle, lsurette, lsvaty, rbalakri, Rhev-m-bugs, sradco, srevivo, ykaul, ylavi
Target Milestone:	ovirt-4.2.0	Keywords:	FutureFeature, Reopened
Target Release:	---	Flags:	sherold: Triaged+ lsvaty: testing_plan_complete+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1475113 (view as bug list)		Environment:
Last Closed:	2018-05-15 17:35:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1475113

Description Bryan Yount 2013-04-11 01:39:10 UTC

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

Comment 2 Barak 2013-06-04 11:41:38 UTC

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.

Comment 7 Shirly Radco 2016-06-01 08:46:11 UTC

Removing support for reports in 4.0.
Will reopen if relevant.

Comment 8 Yaniv Lavi 2016-06-02 13:33:33 UTC

Still relevant. Reopening to track addition to metrics store.

Comment 9 Yaniv Lavi 2016-06-02 13:35:06 UTC

*** Bug 1113772 has been marked as a duplicate of this bug. ***

Comment 10 Yaniv Lavi 2016-06-02 13:35:52 UTC

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.

Comment 11 Yaniv Kaul 2017-06-06 17:14:28 UTC

Shirly, can you provide devel-ack for 4.2?

Comment 12 Shirly Radco 2017-07-10 06:14:17 UTC

These statistics should be provided in the metrics store.
User can create ad hoc reports and dashboards using kibana.

Comment 13 Lukas Svaty 2017-07-11 08:16:29 UTC

should this be cloned upstream?

Comment 14 Shirly Radco 2017-08-02 13:48:05 UTC

Opened upstream bug 1475113

Comment 16 Lukas Svaty 2017-12-08 19:19:29 UTC

tested in ovirt-engine-metrics-1.1.1-0.3.beta2.20171114114644.el7ev.noarch

Comment 20 errata-xmlrpc 2018-05-15 17:35:43 UTC

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

Comment 21 Franta Kust 2019-05-16 13:06:26 UTC

BZ<2>Jira Resync