Bug 1042325 - [RFE][ceilometer]: Add Reporting Capabilities to Ceilometer
Summary: [RFE][ceilometer]: Add Reporting Capabilities to Ceilometer
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/ceil...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:45 UTC by RHOS Integration
Modified: 2015-07-22 17:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 16:52:10 UTC
Target Upstream Version:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.