OpenStack Telemetry (Ceilometer)

Documentation bug - Measurements

Reported by Robert Zaremba on 2012-11-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Medium
Olivier Doutriaux

Bug Description

In the documentation is a bug when lisiting available mesurments:
http://ceilometer.readthedocs.org/en/latest/measurements.html

In the cpu metric row
cpu Cumulative seconds inst ID CPU time used

volume should be nanoseconds instead of seconds,
look -> http://libvirt.org/html/libvirt-libvirt.html#virVcpuInfo

Changed in ceilometer:
status: New → Triaged
importance: Undecided → Medium
tags: added: effort-s
Robert Zaremba (robert.zaremba) wrote :

Should mention that I've already checked the data which are received and they are in nanoseconds.

Changed in ceilometer:
assignee: nobody → Olivier Doutriaux (doutriaux-olivier)

Could i ask you, Robert Zaremba, what is the part of the code which correspond to the cpu metric?

Robert Zaremba (robert.zaremba) wrote :

This is about documentation.

Yes I know, but i'm a newcomer and I wanna be sure my first contribution will be accepted so I am interested in everything related to this bug.

Robert Zaremba (robert.zaremba) wrote :

so check API about cpu metric, the data which will be received.
You can check also counters values in ceilometer storage.
All of them has information about cpu usage in nanoseconds, not in seconds (as it's stayed by documentation)

Doug Hellmann (doug-hellmann) wrote :

Olivier,

The current version of the CPU polling plugin is https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/libvirt.py#L153

There's some documentation about how the compute agent plugins work at http://ceilometer.readthedocs.org/en/latest/contributing/plugins.html#pollster

You've probably already found it, but just in case, the measurement list is documented in https://github.com/openstack/ceilometer/blob/master/doc/source/measurements.rst

Please feel free to ask any other questions on the mailing list! :-)

Thanks,
Doug

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers