From 6cf7bd3935e18d31a66a86f585e64e2ddfe2a81d Mon Sep 17 00:00:00 2001
From: Steven Deaton <sdeaton2@gmail.com>
Date: Wed, 26 Nov 2014 04:04:07 -0600
Subject: [PATCH] Added information for missing Telemtry services.

Added some basic (minimalistic) information about the
rest of the Telemtry-based services that had no listing
prior.

Change-Id: Icbb6cde0b3723b00e9bc0121265ba24d8033b77b
Closes-Bug: 1371004
---
 doc/common/section_getstart_telemetry.xml | 22 +++++++++++++++++-----
 1 file changed, 17 insertions(+), 5 deletions(-)

diff --git a/doc/common/section_getstart_telemetry.xml b/doc/common/section_getstart_telemetry.xml
index d7efb0c90c..d1b34d3cd6 100644
--- a/doc/common/section_getstart_telemetry.xml
+++ b/doc/common/section_getstart_telemetry.xml
@@ -39,7 +39,7 @@
           <listitem><para>Runs on each compute node and polls for resource
           utilization statistics. There may be other types of agents in the
           future, but for now our focus is creating the compute agent.</para>
-        </listitem>
+          </listitem>
         </varlistentry>
         <varlistentry><term>A central agent (<systemitem class="service"
            >ceilometer-agent-central</systemitem>)</term>
@@ -47,6 +47,12 @@
            resource utilization statistics for resources not tied to instances
            or compute nodes.</para></listitem>
         </varlistentry>
+        <varlistentry><term>A notification agent (<systemitem class="service"
+           >ceilometer-agent-notification</systemitem>)</term>
+          <listitem><para>Runs on a central management server to initiate
+          alarm actions, such as calling out to a webhook with a description
+          of the alarm state transition.</para></listitem>
+        </varlistentry>
         <varlistentry><term>A collector (<systemitem class="service"
            >ceilometer-collector</systemitem>)</term>
           <listitem><para>Runs on central management server(s) to monitor the
@@ -55,26 +61,32 @@
            metering messages, which are sent to the message bus using the
            appropriate topic. Telemetry messages are written to the data store
            without modification.</para>
-        </listitem>
+          </listitem>
+        </varlistentry>
+        <varlistentry><term>An alarm evaluator (<systemitem class="service"
+            >ceilometer-alarm-evaluator</systemitem>)</term>
+          <listitem><para>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.</para></listitem>
         </varlistentry>
         <varlistentry><term>An alarm notifier (<systemitem class="service"
             >ceilometer-alarm-notifier</systemitem>)</term>
           <listitem><para>Runs on one or more central management servers to
             allow alarms to be set based on the threshold evaluation for a
             collection of samples.</para></listitem>
-     </varlistentry>
+        </varlistentry>
         <varlistentry>
           <term>A data store</term>
           <listitem><para>A database capable of handling
             concurrent writes (from one or more collector instances)
             and reads (from the API server).</para></listitem>
         </varlistentry>
-          <varlistentry>
+        <varlistentry>
           <term>An API server (<systemitem
            class="service">ceilometer-api</systemitem>)</term>
           <listitem><para>Runs on one or more central management servers to
            provide data access from the data store.</para></listitem>
-      </varlistentry>
+        </varlistentry>
       </variablelist>
       <para>These services communicate by using the OpenStack messaging bus.
         Only the collector and API server have access