The Telemetry Alarming services trigger alarms when the collected metering or event data break the defined rules.<\/p>\n
The Telemetry Alarming service consists of the following components:<\/p>\n
An API server<\/a> (<\/b>aodh-api)\u00a0<\/b>Runs on one or more central management servers to provide access to the alarm information stored in the data store.<\/p>\n An alarm evaluator (<\/b>aodh-evaluator)\u00a0<\/b>Runs on one or more central management servers to determine when alarms fire due to the associated statistic trend crossing a threshold over a sliding time window.<\/p>\n A notification listener (<\/b>aodh-listener)\u00a0<\/b>Runs on a central management server and determines when to fire alarms. The alarms are generated based on defined rules against events, which are captured by the Telemetry Data Collection service\u2019s notification agents.<\/p>\n An alarm notifier (<\/b>aodh-notifier<\/a>)\u00a0<\/b>Runs on one or more central management servers to allow alarms to be set based on the threshold evaluation for a collection of samples.<\/p>\n These services communicate by using the OpenStack messaging bus.<\/p>\n This section describes how to install and configure the Telemetry Alarming service, code-named aodh, on the controller node.<\/p>\n This section assumes that you already have a working OpenStack<\/a> environment with at least the following components installed: Compute, Image Service, Identity.<\/p>\n 1.2.1 Prerequisites\u00a0<\/b><\/p>\n1.2 Install and configure for openSUSE<\/a> and SUSE Linux Enterprise\u00a0<\/a><\/b><\/h3>\n