Bug 1042342

Summary: [RFE][ceilometer]: Monitoring Metrics Object
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/monitoring-metrics-object
Whiteboard: upstream_milestone_next upstream_status_not-started upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:01:12 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:48:48 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/monitoring-metrics-object.

Description:

In Ceilometer, the meters are polled in the form of Counter(namedtuple), do we need two different peer objects or a common lower level object for both meters and metrics?

After the Havana design summit, it's agreed that a common schema will be shared between meters and metrics. So The target of this blueprint is to check and confirm that the customized metrics(openstack-related) will work with the UDP publisher and the common schema. e.g. metrics produced by openstack logging tools, Ganglia, Statsd etc. Bridge the gaps if there is any.

Specification URL (additional information):

https://wiki.openstack.org/wiki/Ceilometer/blueprints/monitoring-metrics-object