Bug 1197638 - [RFE] allow resetting counters for cumulative Tx/Rx statistics
Summary: [RFE] allow resetting counters for cumulative Tx/Rx statistics
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 3.6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Yaniv Lavi
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On: Cumulative_RX_TX_Statistics_VDSM_Engine
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-02 09:43 UTC by Martin Pavlik
Modified: 2016-01-31 12:24 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-31 12:24:22 UTC
oVirt Team: Network
Embargoed:
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

Description Martin Pavlik 2015-03-02 09:43:35 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Martin Pavlik 2015-03-02 09:57:27 UTC 
RHEVM 3.6 should get feature Report total RX/TX byte statistics for hypervisor and VM network interfaces which is solved in Bug 1063343

this feature should be complemented by ability to reset these statistics via RHEVM GUI/REST. So the user can zero them at will. 

For example he decides to move host to new cluster >= 3.6 and wants to begin with zero counters. 

Or decides that he wants to reset the counters first day each month etc...
Comment 2 Lior Vernia 2015-03-02 12:48:21 UTC 
Marking as low priority because users could perform their own accounting with respect to the reported statistics e.g. at the beginning of the month. However, I agree it would be nice to have!
Comment 5 Dan Kenigsberg 2016-01-31 12:24:22 UTC 
Yes, giving the admin more control is nice, but unless a customer proves me wrong, I don't think this is worth the hassle making rx/tx writeable.
Note You need to log in before you can comment on or make changes to this bug.