1.1 Installation Guide 1.1.1 Telemetry Data Collection service overview\u00a0<\/b><\/p>\n
The Telemetry<\/a> Data Collection services provide the following functions:<\/p>\n The Telemetry service consists of the following components:<\/p>\n A compute agent (<\/b>ceilometer-agent-compute)\u00a0<\/b>Runs on each compute node and polls for resource utilization statistics. This is actually the polling agent ceilometer-polling running with parameter –polling-namespace compute.<\/p>\n A central agent (<\/b>ceilometer-agent-central)\u00a0<\/b>Runs on a central management server to poll for resource utilization statistics for resources not tied to instances or compute nodes. Multi- ple agents can be started to scale service horizontally. This is actually the polling agent ceilometer-polling running with parameter –polling-namespace central.<\/p>\n A notification agent (<\/b>ceilometer-agent-notification)\u00a0<\/b>Runs on a central management server(s)<\/a> and consumes messages from the message queue(s) to build event and metering data. Data is then published to defined targets. By default, data is pushed to Gnocchi.<\/p>\n These services communicate by using the OpenStack messaging bus. Ceilometer data is designed to be published to various endpoints for storage and analysis.<\/p>\n Note:\u00a0<\/b>Ceilometer<\/a> previously provided a storage and API<\/a> solution. As of Newton, this functionality is officially deprecated and discouraged. For efficient storage and statistical analysis of Ceilometer data, Gnocchi<\/a> is recommended.<\/p>\n","protected":false},"excerpt":{"rendered":"\n