LUDOC-394 manual: Add meaningful ref names under LustreMonitoring.xml

This patch adds meaningful and proper reference name under file
LustreMonitoring.xml

Signed-off-by: Arshad Hussain <arshad.hussain@aeoncomputing.com>
Change-Id: Iac0e3a9cece98819ec1587fd32ca32d1a1683f2e
Reviewed-on: https://review.whamcloud.com/43435
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Tested-by: jenkins <devops@whamcloud.com>

diff --git a/LustreMonitoring.xml b/LustreMonitoring.xml
index 3d874b5..33e054f 100644 (file)
--- a/LustreMonitoring.xml
+++ b/LustreMonitoring.xml
@@ -7,22 +7,22 @@
     following sections:</para>
   <itemizedlist>
     <listitem>
-      <para><xref linkend="dbdoclet.50438273_18711"/>Lustre Changelogs</para>
+      <para><xref linkend="lustre_changelogs"/>Lustre Changelogs</para>
     </listitem>
     <listitem>
       <para><xref linkend="dbdoclet.jobstats"/>Lustre Jobstats</para>
     </listitem>
     <listitem>
-      <para><xref linkend="dbdoclet.50438273_81684"/>Lustre Monitoring Tool</para>
+      <para><xref linkend="lmt"/>Lustre Monitoring Tool</para>
     </listitem>
     <listitem>
-      <para><xref linkend="dbdoclet.50438273_80593"/>CollectL</para>
+      <para><xref linkend="collectl"/>CollectL</para>
     </listitem>
     <listitem>
-      <para><xref linkend="dbdoclet.50438273_44185"/>Other Monitoring Options</para>
+      <para><xref linkend="other_monitoring_options"/>Other Monitoring Options</para>
     </listitem>
   </itemizedlist>
-  <section xml:id="dbdoclet.50438273_18711">
+  <section xml:id="lustre_changelogs">
       <title><indexterm><primary>change logs</primary><see>monitoring</see></indexterm>
 <indexterm><primary>monitoring</primary></indexterm>
 <indexterm><primary>monitoring</primary><secondary>change logs</secondary></indexterm>
@@ -904,7 +904,7 @@ Configure Auto-cleanup Interval</title>
     <para>The <literal>job_cleanup_interval</literal> can be set as 0 to disable the auto-cleanup. Note that if auto-cleanup of Jobstats is disabled, then all statistics will be kept in memory forever, which may eventually consume all memory on the servers. In this case, any monitoring tool should explicitly clear individual job statistics as they are processed, as shown above.</para>
     </section>
   </section>
-  <section xml:id="dbdoclet.50438273_81684">
+  <section xml:id="lmt">
     <title><indexterm>
         <primary>monitoring</primary>
         <secondary>Lustre Monitoring Tool</secondary>
@@ -918,7 +918,7 @@ Configure Auto-cleanup Interval</title>
     <para><link xl:href="https://github.com/chaos/lmt/wiki">
       https://github.com/chaos/lmt/wiki</link></para>
   </section>
-  <section xml:id="dbdoclet.50438273_80593">
+  <section xml:id="collectl">
     <title>
       <literal>CollectL</literal>
     </title>
@@ -934,7 +934,7 @@ Configure Auto-cleanup Interval</title>
     <para><link xl:href="http://collectl.sourceforge.net/Tutorial-Lustre.html">
       http://collectl.sourceforge.net/Tutorial-Lustre.html</link></para>
   </section>
-  <section xml:id="dbdoclet.50438273_44185">
+  <section xml:id="other_monitoring_options">
     <title><indexterm><primary>monitoring</primary><secondary>additional tools</secondary></indexterm>
 Other Monitoring Options</title>
     <para>A variety of standard tools are available publicly including the following:<itemizedlist>

diff --git a/LustreProc.xml b/LustreProc.xml
index e0834b4..782f2e6 100644 (file)
--- a/LustreProc.xml
+++ b/LustreProc.xml
@@ -2741,7 +2741,7 @@ debug=neterror warning error emerg console</screen>
       <title>Interpreting OST Statistics</title>
       <note>
         <para>See also
-            <xref linkend="dbdoclet.50438273_80593"/> (<literal>collectl</literal>).</para>
+            <xref linkend="collectl"/> (<literal>collectl</literal>).</para>
       </note>
       <para>OST <literal>stats</literal> files can be used to provide statistics showing activity
         for each OST. For example:</para>
@@ -3001,7 +3001,7 @@ ost_write    21   2    59   [bytes] 7648424 15019  332725.08 910694 180397.87
       <title>Interpreting MDT Statistics</title>
       <note>
         <para>See also
-            <xref linkend="dbdoclet.50438273_80593"/> (<literal>collectl</literal>).</para>
+            <xref linkend="collectl"/> (<literal>collectl</literal>).</para>
       </note>
       <para>MDT <literal>stats</literal> files can be used to track MDT
       statistics for the MDS. The example below shows sample output from an