Hi Yurii Thanks for your inputs. Yes, I have noticed that statement in the guide and enabled disable_non_metric_meters in my conf file, but that didn't change the behavior. If you notice, that condition is only applicable for "meters that have a volume as 1". But in my case, the meter that I have defined is of type metric with a proper value for volume.
I think I have found the issue why my meters are not processed by notification agents. If I look at the ceilometer generic meter notification listener module (ceilometer/meter/notifications.py), it listens for all the meters as defined in meters.yaml in the "notifications.info" topic at pre-defined rabbitmq exchanges as defined in ceilometer/exchange_control.py file. But in my case, my service is publishing its meters to "notifications.info" topic at a different exchange name. That means I need to make a change to ceilometer/meter/notifications.py to listen on some default rabbitmq exchange for all non openstack services to publish their telemetry data. So the question is, is there any config that I can use to let "ceilometer/meter/notifications.py" listen on other rabbitmq exchanges in addition to predefined ones, such that this framework can be extended to receive meters from non openstack services? Appreciate your inputs. Thanks Srikanth -----Original Message----- From: Yurii Prokulevych [mailto:[email protected]] Sent: Thursday, January 12, 2017 12:34 AM To: OpenStack Development Mailing List (not for usage questions) <[email protected]> Subject: Re: [openstack-dev] [Ceilometer] Unable to add new metrics using meters.yaml Hi Srikanth, As U've noticed those meters are derived from notifications emitted by other OpenStack services. So please check that 'cord.dns.cache.size' events are processed correctly. Also, the last sentences from the guide: ''' These meters are not loaded by default. To load these meters, flip the `disable_non_metric_meters` option in the ceilometer.conf file ''' Do U have this enabled ? --- Regards, Yurii On Thu, 2017-01-12 at 02:01 +0000, Srikanth Vavilapalli wrote: > Hi > > I was following the instructions @ http://docs.openstack.org/admin-gu > ide/telemetry-data-collection.html#meter-definitions to add new meters > to Ceilometer, but not able to make it work. > > I verified meters.yaml file in meter/data folder: > > ubuntu@mysite-ceilometer-3:/usr/lib/python2.7/dist- > packages/ceilometer/meter/data$ ls > meters.yaml > > > I add the following new meter to the end of that file: > > - name: $.payload.name > event_type: 'cord.dns.cache.size' > type: 'gauge' > unit: 'entries' > volume: $.payload.cache_size > user_id: $.payload.user_id > project_id: $.payload.project_id > resource_id: '"cord-" + $.payload.base_id' > > When I inject 'cord.dns.cache.size' metric from a sample publisher to > rabbitmq server (@ exchange 'openstack') on which the ceilometer > notification agents are listening, I don't see these metrics appearing > in 'ceilometer meter-list' output. Can any one plz let me know if I > missing any config or change that prevents custom meter processing in > Ceilometer? > > Appreciate ur inputs. > > Thanks > Srikanth > > _____________________________________________________________________ > _____ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubs > cribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
