Bug 1168022

Summary:	[RFE]: DWH: tracking comulative CPU usage
Product:	[oVirt] ovirt-engine-dwh	Reporter:	Zaharioudakis Nikos <nzahar>
Component:	RFEs	Assignee:	Shirly Radco <sradco>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Guilherme Santos <gdeolive>
Severity:	low	Docs Contact:
Priority:	medium
Version:	---	CC:	bugs, lleistne, lsurette, sradco, srevivo
Target Milestone:	ovirt-4.4.0	Keywords:	FutureFeature
Target Release:	---	Flags:	pm-rhel: ovirt-4.4? ylavi: planning_ack? pm-rhel: devel_ack+ lleistne: testing_ack+
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-20 20:00:56 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:	1168026

Description Zaharioudakis Nikos 2014-11-25 21:54:24 UTC

Description of problem:

Following a nice discussion in the ovirt mailing list about a billing solution
It would be really nice to be in the position to gather this info per vm so that through an interface GUI invoices could be generated for post paid plans and according to the plans the admin can set. T 

Version-Release number of selected component (if applicable): 1.x :-) meaning it would be a helpful feature to exist already


Expected results: Perhaps a nice minimal billing web app with a separate database that holds the usage information that has the possibility to either generate minimalistic invoices based on plans set by the admin, or access the info through an API from a centralized billing.



Additional info: Interesting aspect would be the actual usage of a customer's vm to be charged in comparison to the provisioned.

Additional info: I picked up the reports as it is the closest component I could think of

Comment 1 Sandro Bonazzola 2019-09-26 13:38:34 UTC

Cpu time for system and user per vm is already collected by metrics store.

Comment 2 RHEL Program Management 2019-09-26 13:38:42 UTC

This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 5 Guilherme Santos 2020-01-02 21:15:46 UTC

Given the fact that metrics-store already collects such information and it's possible to track it through kibana, 
this is verified following the steps:

Steps:
1. Have metrics-store installed and configured for the target engine/host according with tutorial:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/metrics_store_installation_guide/installing_metrics_store
2. Log in into Kibana and select the 'Visualize' tab
3. Create a new visualization with the + sign on the right of the search bar
4. Select a cumulative data visualization chart (such as Area)
5. For the project-* index, Add:
  - Average collectd.cpu.percent for the Y-Axis in metrics 
  - Date Histogram with @timestamp for the X-Axis in sub-buckets
  - collectd.type_instance Term as Split Series in sub-buckets

Results:
Cumulative CPU usage showing in Kibana for the target hosts/engines

Additional Information:
It's possible to filter the visualization even more according with machine or other options that kibana allows,
verification steps above just consider basic filter/information verification

If verification does not seem reflect the RFE and other steps should be followed, feel free to reopen verification.

Comment 6 Sandro Bonazzola 2020-05-20 20:00:56 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.