Hi Gordon,
If I understand what you¹re saying, you think I can try
direct://?publisher=gnocchi in the pipeline.yaml on the controller nodes,
but not the compute nodes to bypass the collector?
When I attempted to do so I received an error (full stack trace ommitted):
2017-06-26 14:52:51.625 41444 ERROR ceilometer.pipeline
[req-e8ac0e01-32f1-4df0-979d-185cd445c7d
5 - - - - -] Pipeline cpu_sink: Continue after error from publisher
<ceilometer.publisher.direct
.DirectPublisher object at 0x29b7b10>
...
2017-06-26 14:52:51.625 41444 ERROR ceilometer.pipeline ProgrammingError:
(pymysql.err.Programmi
ngError) (1146, u"Table 'ceilometer.meter' doesn't exist") [SQL: u'SELECT
meter.id \nFROM meter
\nWHERE meter.name = %(name_1)s AND meter.type = %(type_1)s AND meter.unit
= %(unit_1)s'] [param
eters: {u'type_1': 'gauge', u'name_1': 'cpu_util', u'unit_1': '%'}]
2017-06-26 14:52:51.625 41444 ERROR ceilometer.pipeline
It looks like it¹s attempting to pull something from the mysql table for
ceilometer, which we don¹t have tables for.
On 6/26/17, 6:47 AM, "gordon chung" <g...@live.ca> wrote:
>
>
>On 24/06/17 10:49 PM, Mike Smith wrote:
>> We use ceilometer-compute and we would like to have it push metrics
>>directly to Gnocchi, bypassing the rabbit queues that ceilometer uses in
>>the default Mitaka configuration. Currently our ceilometer-compute
>>pushes to the notification queue, which gets consumed by a ceilometer
>>process and put into the metrics queue, which in turn gets consumed and
>>pushed to gnocchi by the another ceilometer process.
>>
>> We have tried to set the Œpublisher¹ in the ceilometer pipeline.yaml
>>file to gnocchi:// instead of notifier://, but it doesn¹t seem to do
>>anything. No errors or anything, it just doesn¹t seem to try and send
>>metrics to the configured gnocchi endpoint.
>>
>> We are running RDO and have openstack-ceilometer-compute-6.1.3-2.el7.
>>We¹re curious if a different version of openstack-ceilometer-compute is
>>required in order to send metrics directly to gnocchi
>
>changing publiser to gnocchi:// won't work in mitaka. this was only done
>in Ocata i believe. you'd have to backport[1] if you want to use
>gnocchi:// directly. alternatively, you can put direct:// and it should
>allow you to avoid collector service.
>
>that said, you cannot push directly from polling agents -- not without
>some hacking. all the pipeline work is handled by notification agent. if
>you don't need any transformations than it's possible to skip
>notification agent but this requires hacking your code as we do not
>support this. i imagine this would be a welcomed addition, we just don't
>have resources to implement it.
>
>[1]
>https://github.com/openstack/ceilometer/commit/f843b7882fb806cf564c5b3106f
>601815a48c93b
>
>
>--
>gord
>
>_______________________________________________
>OpenStack-operators mailing list
>OpenStack-operators@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
