No worries, it makes me feel better to know I’m not doing something wrong.
Thanks for all the assistance.
On 6/27/17, 6:54 AM, "gordon chung" wrote:
>
>
>On 26/06/17 06:07 PM, Tracy Comstock Roesler wrote:
>> If I understand what you¹re saying, you think I can try
>>
On 26/06/17 06:07 PM, Tracy Comstock Roesler wrote:
> 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?
sorry, i just looked at the code again, it was only
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
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,
Thanks for the response Gordon. I work together with Tracy and can add a
couple of things:
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
On 23/06/17 02:50 PM, Tracy Comstock Roesler wrote:
> We’ve been using gnocchi in mitaka for a few months now but we’ve run
> into some issues with performance, predominantly because of the number
> of data points sent along rabbitmq.
i'm not sure what rabbitmq has to do with gnocchi since