Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1273660 - [RFE] Monitoring Guest CPU steal from the Hypervisor
[RFE] Monitoring Guest CPU steal from the Hypervisor
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs (Show other bugs)
3.5.0
All Linux
low Severity low
: ovirt-4.2.0
: 4.2.0
Assigned To: Rob Young
Liran Rotenberg
: FutureFeature
Depends On:
Blocks: CEECIR_RHV43_proposed
  Show dependency treegraph
 
Reported: 2015-10-20 18:33 EDT by Gajanan
Modified: 2018-05-16 13:01 EDT (History)
15 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-05-15 13:36:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
mavital: testing_plan_complete-


Attachments (Terms of Use)
CPU Usage Percent (162.70 KB, image/png)
2017-12-11 16:20 EST, Shirly Radco
no flags Details
CPU Usage Percent2 (156.26 KB, image/png)
2017-12-11 16:20 EST, Shirly Radco
no flags Details
screenshot_verification (161.16 KB, application/x-xz)
2017-12-26 09:33 EST, Liran Rotenberg
no flags Details


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

  None (edit)
Description Gajanan 2015-10-20 18:33:59 EDT
======= RFE Request ========

1. Proposed title of this feature request  

> Monitoring Guest CPU steal from the Hypervisor
      
      
3. What is the nature and description of the request?  
      
> Customer wants to have the  CPU steal for a vm reported on the on the RHEV-M portal as they want to monitor the CPU-steal within the guest VMs from the hypervisor. 

    
4. Why does the customer need this? (List the business requirements here)  

Customer mentioned:

> We have a several fairly heavily loaded RHEV clusters.  While we collect statistics at the VM level for some of the environments, we don't collect statistics for our "self-service" dev clusters.
We would like to be able to monitor for CPU-steal within the guest VMs from the hypervisor.  
      
    
5. How would the customer like to achieve this? (List the functional requirements here)  

> RHEV-M should report %steal for a vm on the RHEV-M portal. It would be very useful to be able to see the CPU steal from within RHEV-M (either just the APIs or the Web GUI too)
    
    
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
      
    
7. Is there already an existing RFE upstream or in Red Hat Bugzilla ? 

- No 
      
    
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
      
    
9. Is the sales team involved in this request and do they have any additional input?  
      
    
10. List any affected packages or components.  
      
    
11. Would the customer be able to assist in testing this functionality if implemented?
Comment 5 Yaniv Kaul 2017-12-09 10:21:56 EST
Shirly, do we store in Elastic the steal time via the CPU plugin?
Comment 6 Shirly Radco 2017-12-10 07:03:55 EST
No. We currently only report system and user for vms.
Comment 7 Yaniv Kaul 2017-12-10 10:09:19 EST
(In reply to Shirly Radco from comment #6)
> No. We currently only report system and user for vms.

Steal time is reported on the host. Please check if it's available on the CPU plugin and if it can be added.
Comment 8 Shirly Radco 2017-12-11 02:30:04 EST
We collect cpu usage percent by states - steal, interrupt, user, wait, nice, softirq, system, idle.
Comment 9 Yaniv Kaul 2017-12-11 12:20:44 EST
(In reply to Shirly Radco from comment #8)
> We collect cpu usage percent by states - steal, interrupt, user, wait, nice,
> softirq, system, idle.

Excellent - can you attach a screenshot of such an example (even on the Elastic level) and move this to ON_QA for 4.2?
Comment 10 Shirly Radco 2017-12-11 16:20 EST
Created attachment 1366297 [details]
CPU Usage Percent
Comment 11 Shirly Radco 2017-12-11 16:20 EST
Created attachment 1366307 [details]
CPU Usage Percent2
Comment 13 Liran Rotenberg 2017-12-17 04:08:26 EST
Hi,
Shirly screenshots are taken from openshift and not from RHEVM.
I didn't see anything related to "cpu steal" in RHEVM, I checked in the UI dashboard and tried to get any related stats from vdsm to see if it reports anything and i couldn't find any.

Can you please point me where should i look or what to search?
Comment 15 Liran Rotenberg 2017-12-26 09:30:52 EST
Verified on:
RHV: 4.2.0.2-0.1.el7

OpenShift Master:
v3.7.14
Kubernetes Master:
v1.7.6+a08f5eeb62

Steps of verification:
1. Create OpenShift linked to the RHEV environment.
2. In the OpenShift move to applications and click on the logging kibana.
3. In the kibana click on visualize then create the visualization.
4. In the visualization make the new search to be on the RHEV environment.
5. Add the metrics and buckets to use.

For the verification i have made:
1. Area Chart - (metrics)Y-Axis: Max, collectd.cpu.percent;(Buckets) X-Axis: Data Histogram, timestamp, auto; Split-Area: terms, collectd.type_instance, size 6. Then I clicked on the zoom from the right bar into 'cpu steal'.
2. Pie Chart - (metrics)Slice Size: sum, coolectd.cpu.percent;(Buckets) Split Slices: terms, collectd.type_instance, size 10.

Attaching images.
Comment 16 Liran Rotenberg 2017-12-26 09:33 EST
Created attachment 1372468 [details]
screenshot_verification
Comment 20 errata-xmlrpc 2018-05-15 13:36:24 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:1488

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