counter_volume did not represent duration for instance,network,port, subnet, router,

[DongHuai Ren]

Test Steps
I use Web api to check the correction of ceilometer meters.

I find the counter_volume is 1, it did not change. It did not represent the duration of these meters.

Instance, network,subnet,port,router,ip.floating.

    "counter_volume": 1,

Test Investigation:

We find below code in the community. it seems the code set the volume=1 by default.

It did not consistent as the doc described.
http://docs.openstack.org/developer/ceilometer/measurements.html#

def process_notification(self, message):
        instance_type = message.get('payload', {}).get('instance_type')
        if instance_type:
            yield sample.Sample.from_notification(
                name='instance:%s' % instance_type,
                type=sample.TYPE_GAUGE,
                unit='instance',
                volume=1,

 process_notification(self, message):
        LOG.info('network notification %r', message)
        message['payload'] = message['payload'][self.resource_name]
        counter_name = getattr(self, 'counter_name', self.resource_name)
        unit_value = getattr(self, 'unit', self.resource_name)

        yield sample.Sample.from_notification(
            name=counter_name,
            type=sample.TYPE_GAUGE,
            unit=unit_value,
            volume=1,

[Julien Danjou (jdanjou)]

"I find the counter_volume is 1, it did not change. It did not represent the duration of these meters."

Volume is never a duration, it's a quantity. You want to compute duration, use the /statistics endpoint.

[DongHuai Ren (rendh)]

Hi Juline,

have you review with the doc ?
http://docs.openstack.org/developer/ceilometer/measurements.html#

In this doc

Name Type Unit Resource Origin Note
instance Gauge instance inst ID both Duration of instance
instance:<type> Gauge instance inst ID both Duration of instance <type> (openstack types)

[Julien Danjou (jdanjou)]

You are right, this documentation should be fixed. It's true that this meter are used most of the time to compute their duration, but the value is definitely not a time.

[DongHuai Ren (rendh)]

Today I find Volume data not right eigher.Let me sum up here.

couter_volume {instance,instance:<type> ,network,port, subnet, router,ip.floating. volume . }

In this doc, they all described as Duration. I think we can change the doc. Or we add new function to support this beside statics.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/69675

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/69675
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=65ae6da03cfa8e0806c63a1fd6aa3d3a63aa243c
Submitter: Jenkins
Branch: master

commit 65ae6da03cfa8e0806c63a1fd6aa3d3a63aa243c
Author: Pradeep Kilambi <email address hidden>
Date: Tue Jan 28 09:29:42 2014 -0800

    Fix measurement docs to correctly represent Existance meters

    There are various meters in the measurement docs that
    wrongly note the meter as Duration instead of its
    existance. The meters fixed include network, port,
    router, subnet, floating ip, volume.

    fixes bug #1252988

    Change-Id: I45a84769d6ee46d53e580ae08cbbf32ed20562b1