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

Bug 1228991

Summary:	[RFE] Add total RX/TX byte statistics for hypervisor and VM network interfaces to statistics ad hoc domains
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Shirly Radco <sradco>
Component:	ovirt-engine-reports	Assignee:	Shirly Radco <sradco>
Status:	CLOSED ERRATA	QA Contact:	Petr Kubica <pkubica>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	bugs, gklein, lsurette, melewis, rbalakri, Rhev-m-bugs, yeylon, ykaul, ylavi
Target Milestone:	ovirt-3.6.0-rc	Keywords:	FutureFeature
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	3.6.0-beta2	Doc Type:	Enhancement
Doc Text:	With this update the total RX/TX byte statistics for the hypervisor and virtual machine network interfaces have been added to statistics ad hoc domains. This allows users the ability to calculate, for a specific time period, the RX/TX bytes used, per virtual machine or hypervisor interface.	Story Points:	---
Clone Of:	1215587	Environment:
Last Closed:	2016-03-09 21:19:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Reports	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1063343, 1215587
Bug Blocks:	1231509

Description Shirly Radco 2015-06-07 12:07:40 UTC

+++ This bug was initially created as a clone of Bug #1215587 +++

tx_total and tx_total , the total bytes used in vm / hypervisor network interfaces, were added to vds_interface_statistics and vm_interface_statistics.

We want to collect the last samples for each so we can allow the users, for a specific time period calculate the rx/tx used, per vm / hypervisor interface.

Comment 1 Petr Kubica 2015-10-08 09:11:57 UTC

Verified in rhevm-reports-3.6.0-0.6.el6ev.noarch

Comment 3 errata-xmlrpc 2016-03-09 21:19:35 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://rhn.redhat.com/errata/RHEA-2016-0425.html