System Architecture¶

How is data collected?¶

The Ceilometer project created 2 methods to collect data:

1. notification agent which takes messages generated on the notification bus and transforms them into Ceilometer samples or events.

2. polling agent, will poll some API or other tool to collect information at a regular interval. The polling approach may impose significant on the API services so should only be used on optimised endpoints.

The first method is supported by the ceilometer-notification agent, which monitors the message queues for notifications. Polling agents can be configured either to poll the local hypervisor or remote APIs (public REST APIs exposed by services and host-level IPMI daemons).

Notification Agent: Listening for data¶

The heart of the system is the notification daemon (agent-notification) which monitors the message queue for data sent by other OpenStack components such as Nova, Glance, Cinder, Neutron, Swift, Keystone, and Heat, as well as Ceilometer internal communication.

The notification daemon loads one or more listener plugins, using the namespace ceilometer.notification. Each plugin can listen to any topic, but by default, will listen to notifications.info, notifications.sample, and notifications.error. The listeners grab messages off the configured topics and redistributes them to the appropriate plugins(endpoints) to be processed into Events and Samples.

Sample-oriented plugins provide a method to list the event types they’re interested in and a callback for processing messages accordingly. The registered name of the callback is used to enable or disable it using the pipeline of the notification daemon. The incoming messages are filtered based on their event type value before being passed to the callback so the plugin only receives events it has expressed an interest in seeing.

Polling Agent: Asking for data¶

Polling for compute resources is handled by a polling agent running on the compute node (where communication with the hypervisor is more efficient), often referred to as the compute-agent. Polling via service APIs for non-compute resources is handled by an agent running on a cloud controller node, often referred to the central-agent. A single agent can fulfill both roles in an all-in-one deployment. Conversely, multiple instances of an agent may be deployed, in which case the workload is shared. The polling agent daemon is configured to run one or more pollster plugins using any combination of ceilometer.poll.compute, ceilometer.poll.central, and ceilometer.poll.ipmi namespaces

The frequency of polling is controlled via the polling configuration. See Polling for details. The agent framework then passes the generated samples to the notification agent for processing.

Pipeline Manager¶

Ceilometer offers the ability to take data gathered by the agents, manipulate it, and publish it in various combinations via multiple pipelines. This functionality is handled by the notification agents.

Publishing the data¶

Currently, processed data can be published using different transport options:

1. gnocchi, which publishes samples/events to Gnocchi API;

2. notifier, a notification based publisher which pushes samples to a message queue which can be consumed by an external system;

3. udp, which publishes samples using UDP packets;

4. http, which targets a REST interface;

5. file, which publishes samples to a file with specified name and location;

6. zaqar, a multi-tenant cloud messaging and notification service for web and mobile developers;

7. https, which is http over SSL and targets a REST interface;

8. prometheus, which publishes samples to Prometheus Pushgateway;

9. monasca, which publishes samples to the Monasca API.