Bug 1042325

Summary: [RFE][ceilometer]: Add Reporting Capabilities to Ceilometer
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/ceilometer/+spec/add-ceilometer-reporter
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:52:10 UTC 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:45:27 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/add-ceilometer-reporter.

Description:

As part of StackTach integration, Ceilometer should have a similar feature to StackTach's reporting, where we can leverage the stored event and sample data to summarize the event stream we're monitoring. Things like Nova operation failures, state transition timings, etc. should be summarized and reported on to provide operators more insight into the health of their cloud, as well as problem areas to focus on (especially helpful when contributing back to OpenStack).

The reporting capability needs to be easily extendable, which seems handled well by the trigger manager and event pipelines to come. We will be able to summarize as we go and keep the report piece itself pretty thin. For example, instead of the report determining a failed build like it currently does in StackTach, we can instead just trigger a instance.build.failed event or sample when the event stream processing finds that a build has failed. Then, in the report, we can just count the number of failed builds and successful builds to report on build failure percentage.

Specification URL (additional information):

None