Bug 1042268

Summary: [RFE][ceilometer]: Rate-per-second gauge meters derived from cumulative samples
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-ceilometerAssignee: RHOS Maint <rhos-maint>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, jruzicka, markmc, pbrady, yeylon
Target Milestone: gaKeywords: FutureFeature
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/ceilometer/+spec/rates-derived-from-cumulative
Whiteboard: upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 21:35:27 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/rates-derived-from-cumulative.

Description:

Currently we capture several detailed metrics related to disk & network I/O from the hypervisor in cumulative form, specifically:

* disk.read.requests
* disk.write.requests
* disk.read.bytes
* disk.write.bytes
* network.incoming.bytes
* network.outgoing.bytes
* network.incoming.packets
* network.outgoing.packets

These values being cumulative are not suitable for alarming against with the static style of alarm threshold that ceilometer supports. Cumulative values are not best suited to charting either via the new metering dashboard as trends are less easy to spot visually.

However we could follow the pattern used to derived cpu_util from cpu samples via the rate_of_change transformer to produce derived meters based on the rate of bytes or packets flowing per second. Such gauge meters would be much more useful from an alarming and dashboarding perspective.

Specification URL (additional information):

None