I found a way to do it using the documentation at
http://docs.openstack.org/admin-guide-cloud/content/section_telemetry-pipeline-transformers.html#d6e11759.
The trick was to use arithmetic and the $(cpu).resource_metadata.vcpus.
- name: hs06_sink
transformers:
- name:
I am just curious have you restarted ceilometer services after
pipeline.yaml has been changed?
Igor Degtiarov
Software Engineer
Mirantis Inc
www.mirantis.com
On Sat, Mar 21, 2015 at 1:21 PM, Tim Bell tim.b...@cern.ch wrote:
No errors in the notification logs.
Should this work with the
No errors in the notification logs.
Should this work with the default ceilometer.conf file or do I need to enable
anything ?
I've also tried using arithmetic. When I have a meter like cpu for the
source, this fires the expression evaluation without problems. However, I can't
find a good way
I'm running Juno with ceilometer and trying to produce a new meter which is
based on vcpus * F (where F is a constant that is different for each
hypervisor).
When I create a VM, I get a new sample for vcpus.
However, it does not appear to fire the transformer.
The same approach using cpu
Hi Tim
I've check your case on my devstack. And I've received new hs06 meter
in my meter list.
So something wrong with your local env.
Cheers,
Igor D.
Igor Degtiarov
Software Engineer
Mirantis Inc
www.mirantis.com
On Fri, Mar 20, 2015 at 5:40 PM, Tim Bell tim.b...@cern.ch wrote:
I’m
i can confirm it works for me as well... are there any noticeable errors in the
ceilometer-agent-notifications log? the snippet below looks sane to me though.
cheers,
gord
From: idegtia...@mirantis.com
Date: Fri, 20 Mar 2015 18:35:56 +0200
To: openstack-dev@lists.openstack.org
Subject: Re:
