Chapter 12. Install the Telemetry Service


12.1. Overview of Telemetry Service Deployment

The Telemetry service is composed of an API service, three openstack-ceilometer agents, and two alarm services. The API service (provided by the openstack-ceilometer-api package) runs on one or more central management servers to provide access to the Telemetry database.

Note

At present, mongod is the only database service supported by the Telemetry service.
The three Telemetry agents (and their respective packages) are listed below:
  • The Central agent (provided by openstack-ceilometer-central) runs on a central management server to poll public REST APIs for utilization statistics about resources that are not visible (either through notifications or from the hypervisor layer).
  • The Collector (provided by openstack-ceilometer-collector) runs on one or more central management servers to receive notifications on resource usage. The Collector also parses resource usage statistics and saves them as datapoints in the Telemetry database.
  • The Compute agent (provided by openstack-ceilometer-compute) runs on each Compute service node to poll for instance utilization statistics. You must install and configure the Compute service before installing the openstack-ceilometer-compute package on any node.
The two alarm services (and their respective packages) that comprise the rest of the Telemetry service are listed below:
  • The Evaluator (provided by ceilometer-alarm-evaluator) triggers state transitions on alarms.
  • The Notifier (provided by ceilometer-alarm-notifier) executes required actions when alarms are triggered.
You must configure the following settings for each of the components:
  • Authentication, including the Identity service tokens and Telemetry secret
  • The database connection string, for connecting to the Telemetry database
The authentication settings and database connection string for these components are all configured in /etc/ceilometer/ceilometer.conf. As such, components deployed on the same host will share the same settings. If Telemetry components are deployed on multiple hosts, you must replicate any authentication changes to these hosts by copying the ceilometer.conf file to each host after applying the new settings.
Once the Telemetry service (all of its components, wherever each is hosted) is deployed and configured, you must configure each monitored service (Image, Networking, Object Storage, Block Storage, and each Compute node) to submit data to the Telemetry service. The related settings are configured in each service's configuration file.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.