12.8. Configure Monitored Services

⁠12.8. Configure Monitored Services

The Telemetry service can also monitor the Image, Networking, Object Storage, and Block Storage service. To enable this, you will need to configure each service to submit samples to the Collector services. The following commands demonstrate how to do this for each service. Before configuring any of these services, install the python-ceilometer and python-ceilometerclient packages on the node hosting the service first:

# yum install python-ceilometer python-ceilometerclient

Note

Restart a service after configuring it to be monitored by the Telemetry service. Doing so will allow the configuration to take effect.

Image service (glance)

# openstack-config --set /etc/glance/glance-api.conf \
	DEFAULT notifier_strategy NOTIFYMETHOD

Replace NOTIFYMETHOD with a notification queue: rabbit (to use a rabbitmq queue) or qpid (to use a qpid message queue).

Block Storage service (cinder)

# openstack-config --set /etc/cinder/cinder.conf \	
	DEFAULT notification_driver cinder.openstack.common.notifier.rpc_notifier
# openstack-config --set /etc/cinder/cinder.conf \	
	DEFAULT rpc_backend cinder.openstack.common.rpc.impl_qpid
# openstack-config --set /etc/cinder/cinder.conf \	
	DEFAULT control_exchange cinder

Object Storage service (swift)

The Telemetry service collects samples from the Object Storage service (swift) through the ResellerAdmin role. The steps to configure this should already have been performed when configuring the required Identity records for Telemetry.

In addition, you will also need to configure the Object Storage service to process traffic from ceilometer. To do so:

⁠

Procedure 12.4. Configuring the Object Storage service to process traffic from the Telemetry service

Add the following line to /etc/swift/proxy-server.conf:
```
[filter:ceilometer]
use = egg:ceilometer#swift
```

Add ceilometer to the pipeline directive of the same file:

[pipeline:main]
pipeline = healthcheck cache authtoken keystoneauth proxy-server ceilometer

Networking service (neutron)

Telemetry supports the use of labels for distinguishing IP ranges. Use openstack-config to enable Networking integration with Telemetry:

# openstack-config --set /etc/neutron/neutron.conf \	
	DEFAULT notification_driver neutron.openstack.common.notifier.rpc_notifier