Backlog #2688

Network statistics reported by oneacct are not accumulated

Added by Dirk Daems over 6 years ago. Updated almost 4 years ago.

Status:ClosedStart date:01/29/2014
Priority:HighDue date:
Assignee:Tino Vázquez% Done:

0%

Category:Drivers - Monitor
Target version:-

Description

Looking at the vm_monitoring table in the sqlite db, it becomes clear that the NET_RX and NET_TX values reported by oneacct are not accumulated and their value is the aggregation of the last 300 * 5 ms: start_time = Time.now - 300 * 5
This is not in line with the oneacct documentation.

History

#1 Updated by Tino Vázquez over 6 years ago

  • Affected Versions OpenNebula 4.4 added

#2 Updated by Dirk Daems over 6 years ago

Also noticed that the value of the NET_TX element in the vm_monitoring table is always zero bytes, which causes the value in the oneacct output to be zero as well of course.
Might be specific to the VMware network driver implementation as this driver was used for testing?

#3 Updated by Ruben S. Montero over 6 years ago

  • Status changed from Pending to New
  • Target version set to Release 4.8

We can confirm this issue, it is something vmware specific. We'll look for a better way to obtain the performance counters

#4 Updated by Ruben S. Montero over 6 years ago

  • Category changed from Core & System to Drivers - Monitor

#5 Updated by Ruben S. Montero over 6 years ago

  • Assignee set to Tino Vázquez

#6 Updated by Tino Vázquez about 6 years ago

  • Tracker changed from Bug to Backlog
  • Priority changed from Normal to High
  • Target version deleted (Release 4.8)

#7 Updated by Ruben S. Montero about 6 years ago

  • Status changed from New to Pending

#8 Updated by Miguel Ángel Álvarez Cabrerizo almost 4 years ago

  • Status changed from Pending to Closed

In OpenNebula 5.2 NETTX and NETRX are gathered from vCenter's Performance Manager and they are accumulated with previous monitored values.

Solved in ticket: http://dev.opennebula.org/issues/4943

Also available in: Atom PDF