Bug 950813 – [RFE] Metrics should include information about the RHV-M server (CPU, memory, network, etc.)

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 950813 - [RFE] Metrics should include information about the RHV-M server (CPU, memory, network, etc.)

Summary:	[RFE] Metrics should include information about the RHV-M server (CPU, memory,...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine-metrics (Show other bugs)
Sub Component:
Version:	3.1.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	ovirt-4.2.0
Target Release:	---
Assigned To:	Shirly Radco
QA Contact:	Lukas Svaty
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature, Reopened

Duplicates:	1113772 (view as bug list)
Depends On:
Blocks:	1475113
	Show dependency tree / graph

Reported:	2013-04-10 21:39 EDT by Bryan Yount
Modified:	2018-05-15 13:35 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Clones:	1475113 (view as bug list)
Environment:
Last Closed:	2018-05-15 13:35:43 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Metrics
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	sherold: Triaged+ lsvaty: testing_plan_complete+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2018:1486	None	None	None	2018-05-15 13:35 EDT

Groups: None (edit)

Description Bryan Yount 2013-04-10 21:39:10 EDT

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 07:41:38 EDT

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 04:46:11 EDT

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

Comment 8 Yaniv Lavi 2016-06-02 09:33:33 EDT

Still relevant. Reopening to track addition to metrics store.

Comment 9 Yaniv Lavi 2016-06-02 09:35:06 EDT

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

Comment 10 Yaniv Lavi 2016-06-02 09:35:52 EDT

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 13:14:28 EDT

Shirly, can you provide devel-ack for 4.2?

Comment 12 Shirly Radco 2017-07-10 02:14:17 EDT

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 04:16:29 EDT

should this be cloned upstream?

Comment 14 Shirly Radco 2017-08-02 09:48:05 EDT

Opened upstream bug 1475113

Comment 16 Lukas Svaty 2017-12-08 14:19:29 EST

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

Comment 20 errata-xmlrpc 2018-05-15 13:35:43 EDT

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

Note You need to log in before you can comment on or make changes to this bug.