diff --git a/doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml b/doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml
index 5495acc0d0..5b339caaaf 100644
--- a/doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml
+++ b/doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml
@@ -74,6 +74,24 @@
         <para>These are a lightweight alternative to webhooks, whereby the state transition is simply logged by the <systemitem class="service">alarm-notifier</systemitem>, and are intended primarily for testing purposes.</para>
       </section>
     </section>
+    <section xml:id="section_telemetry-alarm-workload-partitioning">
+      <title>Workload partitioning</title>
+      <para>The alarm evaluation process uses the same mechanism for
+        workload partitioning as the central and compute agents.
+        The <link xlink:href="https://pypi.python.org/pypi/tooz">
+        Tooz</link> library provides the coordination within the
+        groups of service instances. For further information
+        about this approach see
+        <xref linkend="section_telemetry-cetral-compute-agent-ha"/>.
+        </para>
+      <para>To use this workload partitioning solution set the
+        <option>evaluation_service</option> option to <literal>
+        default</literal>. For more information, see the alarm
+        section in the
+        <link xlink:href="http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-telemetry.html">
+        <citetitle>OpenStack Configuration Reference</citetitle></link>.
+        </para>
+    </section>
   </section>
   <section xml:id="section_telemetry-alarm-usage">
     <title>Using alarms</title>