Does Openstack provides statastics for "network.incoming.packets.rate" meter for VMWare instance using ceilometer api?

asked 2016-04-11 01:30:52 -0600

Sandeep gravatar image

Does Openstack provides statastics for "network.incoming.packets.rate" meter for VMWare instance using ceilometer api?

I have setup where I have configured two compute node, one for KVM and one for VMWare. I am able to get "network.incoming.packets.rate" meters for KVM using ceilometer api but not for VMware. Does Openstack provides statastics for "network.incoming.packets.rate" meter for VMWare instance using ceilometer api?

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2016-04-12 07:11:11 -0600

Sandeep gravatar image

updated 2016-04-12 07:13:44 -0600

Hi yprokule's,

I did lot of debugging and found network_incoming_packets_rate and network_outgoing_packet_rate metric not supported by vSphere inspector. I checked for KVM and i can see all network related metric like: site-packages/ceilometer/compute/virt/libvirt/ dom_stats = domain.interfaceStats(name) stats = virt_inspector.InterfaceStats(rx_bytes=dom_stats[0], rx_packets=dom_stats[1], tx_bytes=dom_stats[4], tx_packets=dom_stats[5])

For Vmware-> site-packages/ceilometer/compute/virt/vmware/ stats = virt_inspector.InterfaceRateStats(rx_bytes_rate, tx_bytes_rate)

Please help here because in openstack doc its clearly mention packet rate metric supported for Vmware but in python code its missing.

edit flag offensive delete link more


@Sandeep, I'm not sure about the code. Does this call returns U a network.incoming.(packets|bytes) meters?

ceilometer meter-list -q 'resource-id=<$VM_ID> ?

If not, please enable debug/verbose on the compute node, restart ceilometer* services and check logs for more detail.

Regards, Yurii

yprokule gravatar imageyprokule ( 2016-04-13 09:22:22 -0600 )edit

answered 2016-04-12 01:34:19 -0600

yprokule gravatar image

@Sandeep, ceilometer's api will return U all the data it hat(actually what U r authorized to access)

According to network.incoming.packets.rate counter is supported. Though - this one is created by rate_of_change transformer in pipeline.yaml.

So, I'd like U to check your pipeline.yaml on compute/controller nodes and enable debug/verbose logging for ceilometer.

edit flag offensive delete link more


  • name: network_source interval: 60 meters: - "network.incoming.bytes" - "network.incoming.packets" - "network.outgoing.bytes" - "network.outgoing.packet
Sandeep gravatar imageSandeep ( 2016-04-12 04:01:30 -0600 )edit
  • name: network_sink transformers: - name: "rate_of_change" parameters: source: map_from: name: "network\.(incoming|outgoing)\.(bytes|packets)" unit: "(B|packet)"
Sandeep gravatar imageSandeep ( 2016-04-12 04:01:51 -0600 )edit

target: map_to: name: "network.\1.\2.rate" unit: "\1/s" type: "gauge"

Sandeep gravatar imageSandeep ( 2016-04-12 04:02:04 -0600 )edit

Thanks for your help i can not see option to post complete pipeline.yaml so i only posted network related part

Sandeep gravatar imageSandeep ( 2016-04-12 04:31:43 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-04-11 01:30:52 -0600

Seen: 529 times

Last updated: Apr 12 '16