Bug 1278312 - [RFE] - Display Total RX/TX statistics for vlan networks
Summary: [RFE] - Display Total RX/TX statistics for vlan networks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: RFEs
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ovirt-4.4.1
: ---
Assignee: Shirly Radco
QA Contact: Guilherme Santos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-05 09:00 UTC by Michael Burman
Modified: 2020-08-05 06:25 UTC (History)
5 users (show)

Fixed In Version: rhv-4.4.0-29
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-05 06:25:08 UTC
oVirt Team: Metrics
Embargoed:
sbonazzo: ovirt-4.4?
mburman: planning_ack?
mburman: devel_ack?
lleistne: testing_ack+


Attachments (Terms of Use)

Description Michael Burman 2015-11-05 09:00:03 UTC
Description of problem:
[RFE] - Display Total RX/TX statistics for bond interfaces and for vlan networks.

At current 3.6.0 release this is still not implemented and it should. 
- Today total rx/tx statistics reported for each slave of the bond, but not for the bond interface. 
- We don't have total rx/tx statistics for vlan networks, so if we have multiple vlan networks attached to NIC/bond, the counters displays the NICs or the slaves total rx/tx statistics and not the vlan networks.
User might want to know how much traffic passes over his networks.

Version-Release number of selected component (if applicable):
3.6.0.3-0.1.el6

How reproducible:
100

Comment 2 Yaniv Lavi 2016-11-23 10:41:19 UTC
Moving to DWH as we would like this metric as part of the metric store.

Comment 3 Sandro Bonazzola 2019-09-26 13:43:44 UTC
This can be already accumulated in kibana with data collected by metrics store.

Comment 9 Guilherme Santos 2020-07-11 13:30:37 UTC
I'm verifying considering that an external ES instance have been tested and all the request data already gets to ES (either external or not)
If any further verification is needed, we can reopen and target to 4.4.2.

Comment 11 Sandro Bonazzola 2020-08-05 06:25:08 UTC
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 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.


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