Ceilometer configuration

Ceilometer is a required OpenStack services for Fleio. It gathers data and metrics about services and sends it to Gnocchi used by Fleio for billing.

Please check the Ceilometer ceilometer.conf, pipeline.yaml , polling.yaml and the gnocchi_resources.yaml to make sure settings are similar to what’s shown below.


Under the [DEFAULT] section, make sure the dispatcher is set o gnocchi

event_dispatchers = gnocchi
meter_dispatchers = gnocchi

Under the [api] section also make sure gnocchi is enabled

gnocchi_is_enabled = True

Fleio expects a specific Gnocchi archive policy. Create a new archive policy named fleio_policy and set it as default (fleio_policy is just an example, you can use any name you want)

gnocchi archive-policy create -d granularity:5m,points:290 -d granularity:30m,points:336 -d granularity:1h,points:768 -m max -m mean -m sum fleio_policy
gnocchi archive-policy-rule create -a fleio_policy -m '*' default

The [notifications] settings should be similar to:

# Notification queues to listen on
# Ceilometer needs to connect to it's own notification RabbitMQ vhost and to all RabbitMQ vhosts that exists for all services
# Do not confuse a RabbitMQ vhost with normal virtual host or server. RabbitMQ can have it's own vhosts like /swift /nova, /cinder as shown below.
# If only one vhost exists, there is no need to add multiple messaging_urls
messaging_urls = rabbit://ceilometer:password@rabbitip:5672//ceilometer?
messaging_urls = rabbit://swift:password@rabbitip:5672//swift
messaging_urls = rabbit://nova:password@rabbitip:5672//nova?
messaging_urls = rabbit://cinder:password@rabbitip:5672//cinder?
messaging_urls = rabbit://neutron:password@rabbitip:5672//neutron?
store_events = False
workers = 3  # set to a value according to your load



This may not be needed, depending on your OpenStack distribution. This was tested, and it is required for OpenStack-Ansible deployment.

We chose to leave the file empty since it was filling the rabbitmq pool with unnecessary notifications.



This may not be needed, depending on your OpenStack distribution. This was tested and it is required for OpenStack-Ansible deployment.

For an example of the event definition file access: https://github.com/openstack/ceilometer/blob/master/ceilometer/pipeline/data/event_definitions.yaml


Bellow you can find an example of pipeline configuration that should work in most cases:

  - name: cpu_sink
      - gnocchi://?filter_project=service&archive_policy=fleio_policy
  - name: network_sink
      - gnocchi://?filter_project=service&archive_policy=fleio_policy
  - interval: 60
      - cpu
      - vcpus
    name: cpu_source
      - cpu_sink
  - interval: 60
      - network.incoming.bytes
      - network.incoming.packets
      - network.outgoing.bytes
      - network.outgoing.packets
    name: network_source
      - network_sink

Please note that you must specify the archive-policy directly from pipeline.yml. With the above configuration you will have measurements for cpu, vcpu, network.incoming.bytes, network.incoming.packets, network.outgoing.bytes, network.outgoing.packets.

Also, in order to correctly configure pipeline.yml, please check the gnocchi.conf to get the project_name. In our case is project_name = service (used in pipeline.yml filter_project=service)



This may not be needed, depending on your OpenStack distribution. This was tested, and it is required for OpenStack-Ansible deployment.

In order to be able to send the new metrics to Gnocchi, we need to make the Gnocchi dispatcher aware of our new metrics.

The default file for your OpenStack version can be used.


The polling.yaml file is used by the ceilometer polling agent to gather and process metrics before sending them to Gnocchi.

Here is an example of polling.yaml file:

    - name: some_pollsters
      interval: 300
        - cpu
        - cpu_l3_cache
        - memory.usage
        - network.incoming.bytes
        - network.incoming.packets
        - network.outgoing.bytes
        - network.outgoing.packets
        - disk.device.read.bytes
        - disk.device.read.requests
        - disk.device.write.bytes
        - disk.device.write.requests
        - hardware.cpu.util
        - hardware.memory.used
        - hardware.memory.total
        - hardware.memory.buffer
        - hardware.memory.cached
        - hardware.memory.swap.avail
        - hardware.memory.swap.total
        - hardware.system_stats.io.outgoing.blocks
        - hardware.system_stats.io.incoming.blocks
        - hardware.network.ip.incoming.datagrams
        - hardware.network.ip.outgoing.datagrams
        - storage.objects
        - storage.objects.size
        - storage.objects.containers
        - storage.containers.objects
        - storage.containers.objects.size

Notice the storage.* meters. These are used by Fleio to account for and Swift usage.

After setting up Ceilometer, restart the ceilometer-notification-agent and ceilometer-polling and check the metrics. Additional configuration may be required for swift.

See the OpenStack documentation for how to setup Ceilometer to connect to Swift with the ResellerAdmin role to gather data.

If you are having issues with the metrics please see Ceilometer troubleshooting.