Bug 1596033

Summary:	Ceilometer creates metrics that will never get measures
Product:	Red Hat OpenStack	Reporter:	Mehdi ABAAKOUK <mabaakou>
Component:	openstack-ceilometer	Assignee:	Mehdi ABAAKOUK <mabaakou>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	jruzicka, mabaakou, mariel, mmagr, sclewis, srevivo
Target Milestone:	Upstream M3	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ceilometer-11.0.1-0.20180816141555.786f90c.el7ost	Doc Type:	Bug Fix
Doc Text:	The OpenStack Metrics service (Ceilometer) created metrics that were not measured by the Monitoring service (Gnocchi). This fix removes the unnecessary metrics. Now, Ceilometer creates only metrics that will be measured by Gnocchi.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:50:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mehdi ABAAKOUK 2018-06-28 06:05:15 UTC

Description of problem:

Ceilometer creates metrics that will never get measures. 

This confuses a lot people.

Comment 5 Sasha Smolyak 2018-10-18 09:37:34 UTC

May I get the list of deleted metrics in order to check that they don't appear anymore? Or a list of metrics to stay. Does it mean that now every metric must have measures?

Comment 6 Mehdi ABAAKOUK 2018-10-18 09:42:35 UTC

It's a bit hard have the list of deleted metric since it depends on so many thing outside Ceilometer/Gnocchi. So, yes check that every metric have measures looks a good approach to me.

Comment 7 Sasha Smolyak 2018-10-31 13:07:31 UTC

Created several instances, checked measures for all the metrics, measures exist. Verified

Comment 10 errata-xmlrpc 2019-01-11 11:50:23 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045