MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:john.russell Date:January 19 2011 10:34pm
Subject:svn commit - mysqldoc@docsrva: r24849 - trunk/mysql-monitor-2.2
View as plain text  
Author: jrussell
Date: 2011-01-19 23:34:38 +0100 (Wed, 19 Jan 2011)
New Revision: 24849

Log:
Backported some more index entries and editorial changes.


Modified:
   trunk/mysql-monitor-2.2/dashboard-advisors.xml
   trunk/mysql-monitor-2.2/dashboard-events.xml
   trunk/mysql-monitor-2.2/dashboard-graphs.xml
   trunk/mysql-monitor-2.2/dashboard-overview.xml
   trunk/mysql-monitor-2.2/dashboard-query-analyzer.xml
   trunk/mysql-monitor-2.2/dashboard-replication.xml
   trunk/mysql-monitor-2.2/dashboard-settings.xml
   trunk/mysql-monitor-2.2/dashboard-whatsnew.xml


Modified: trunk/mysql-monitor-2.2/dashboard-advisors.xml
===================================================================
--- trunk/mysql-monitor-2.2/dashboard-advisors.xml	2011-01-19 18:25:57 UTC (rev 24848)
+++ trunk/mysql-monitor-2.2/dashboard-advisors.xml	2011-01-19 22:34:38 UTC (rev 24849)
Changed blocks: 2, Lines Added: 6, Lines Deleted: 1; 695 bytes

@@ -9,6 +9,10 @@
 
   <title>The <guilabel>Advisors</guilabel> Tab</title>
 
+  <indexterm>
+    <primary>Advisors tab</primary>
+  </indexterm>
+
   <note>
     <para>
       &commercial_blurb;

@@ -25,7 +29,8 @@
   </para>
 
   <para>
-    The MySQL Enterprise Advisors fall into the following categories:
+    The MySQL Enterprise Advisors are grouped into the following
+    categories:
   </para>
 
   <itemizedlist>


Modified: trunk/mysql-monitor-2.2/dashboard-events.xml
===================================================================
--- trunk/mysql-monitor-2.2/dashboard-events.xml	2011-01-19 18:25:57 UTC (rev 24848)
+++ trunk/mysql-monitor-2.2/dashboard-events.xml	2011-01-19 22:34:38 UTC (rev 24849)
Changed blocks: 15, Lines Added: 94, Lines Deleted: 100; 16680 bytes

@@ -9,6 +9,10 @@
 
   <title>The <guilabel>Events</guilabel> Tab</title>
 
+  <indexterm>
+    <primary>Events tab</primary>
+  </indexterm>
+
   <remark role="dynamic-dependency-list"/>
 
   <note>

@@ -18,13 +22,13 @@
   </note>
 
   <para>
-    Once an advisor has been scheduled, it will run at set intervals. If
-    it finds nothing of interest no alerts or emails will be created.
+    Once an advisor is scheduled, it runs at set intervals. If it finds
+    nothing of interest, it creates no alerts or emails.
   </para>
 
   <para>
     Events are defined using a number of different levels according to
-    the severity of the alert. The seven levels are
+    the severity of the alert. The seven levels are:
   </para>
 
   <itemizedlist>

@@ -32,9 +36,9 @@
     <listitem>
       <para>
         <emphasis role="bold">Failure</emphasis>: Indicates a failure
-        for the given rule or event. Usually this indicates that the
+        for the given rule or event. Usually, this indicates that the
         rule on which the event is based has failed, probably due to a
-        typo or other error. Occasionally it can indicate a failure to
+        typo or other error. Occasionally, it can indicate a failure to
         retrieve the required information for a given rule.
       </para>
     </listitem>

@@ -43,45 +47,42 @@
       <para>
         <emphasis role="bold">Critical</emphasis>: The event is critical
         and requires immediate attention. Critical events normally
-        indicate that a serious problem has, or is about, to occur. You
-        should examine the event and determine the cause and fix it as
-        soon as possible.
+        indicate that a serious problem has occurred or is about to
+        occur. Examine the event, determine the cause, and fix the issue
+        as soon as possible.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        <emphasis role="bold">Warning</emphasis>: The event is a warning
-        of something that you should be aware of, but which is not
-        affecting the operation of your server.
+        <emphasis role="bold">Warning</emphasis>: The event is something
+        that you should be aware of, but does not affect the operation
+        of your server.
       </para>
     </listitem>
 
     <listitem>
       <para>
         <emphasis role="bold">Info</emphasis>: The event is for
-        informational purposes. Info events are used to indicate issues
-        that do not affect the operation of your server, but which may
-        highlight a minor configuration or other issue.
+        informational purposes. Info events call attention to issues
+        that do not affect the operation of your server, such as a minor
+        configuration issue.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        <emphasis role="bold">Success</emphasis>: The rule has executed
-        successfully with no issues. This is used to indicate that the
-        result of the rule is OK and is used to indicate when an event
-        that was previously in a Critical or Failure state has returned
-        to normal.
+        <emphasis role="bold">Success</emphasis>: The rule executed
+        successfully with no issues. The result of the rule is OK. It
+        also signals when an event that was previously in a Critical or
+        Failure state returns to normal.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        <emphasis role="bold">Unknown</emphasis>: Indicates when the
-        current state of the event/rule is currently unknown. This state
-        can be issued when the current status of the event cannot be
-        determined.
+        <emphasis role="bold">Unknown</emphasis>: The current status of
+        the event/rule cannot be determined.
       </para>
     </listitem>
 

@@ -96,12 +97,12 @@
 
   <para>
     For convenience, the event states are also represented by icons, as
-    defined in the table below. The table also shows the relative level
-    of the alert from the highest (Critical) to the lowest (unknown).
-    The order represented here is used when identifying when an event
-    has transitioned between levels (for example, from Success to
-    Critical), hence triggering a notification, and when sorting events
-    based on their current state.
+    defined in the following table. The table also shows the relative
+    level of the alert from the highest (Critical) to the lowest
+    (Unknown). The order represented here is used when identifying when
+    an event has transitioned between levels (for example, from Success
+    to Critical), hence triggering a notification, and when sorting
+    events based on their current state.
   </para>
 
   <informaltable>

@@ -133,7 +134,7 @@
               </imageobject>
 
             </inlinemediaobject></entry>
-          <entry>A triangular yellow icon a warning.</entry>
+          <entry>A triangular yellow icon indicates a warning.</entry>
         </row>
         <row>
           <entry><inlinemediaobject>

@@ -176,7 +177,7 @@
     <guilabel>Monitor</guilabel> screen in order of severity. The
     notification group or groups associated with a specific rule receive
     email notification when an alert is triggered. For more information
-    about creating notification groups see
+    about creating notification groups, see
     <xref linkend="mem-notification-groups"/>.
   </para>
 

@@ -208,61 +209,61 @@
     <listitem>
       <para>
         <guilabel>Current</guilabel>: An icon indicating the current
-        severity of the alert
+        severity of the alert.
       </para>
     </listitem>
 
     <listitem>
       <para>
         <guilabel>Worst</guilabel>: An icon indicating the worst
-        severity recorded for this alert
+        severity recorded for this alert.
       </para>
     </listitem>
 
     <listitem>
       <para>
         <guilabel>Severity</guilabel>: An icon indicating the severity
-        of the alert
+        of the alert.
       </para>
     </listitem>
 
     <listitem>
       <para>
         <guilabel>Server</guilabel>: The name of the server the alert
-        applies to
+        applies to.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        <guilabel>Advisor</guilabel>: The category of the advisor
+        <guilabel>Advisor</guilabel>: The category of the advisor.
       </para>
     </listitem>
 
     <listitem>
       <para>
         <guilabel>Rule</guilabel>: A short description of the rule that
-        has been violated
+        is violated.
       </para>
     </listitem>
 
     <listitem>
       <para>
         <guilabel>Time</guilabel>: The approximate time the event
-        occurred
+        occurred.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        <guilabel>Status</guilabel>: The status of the event
+        <guilabel>Status</guilabel>: The status of the event.
       </para>
     </listitem>
 
     <listitem>
       <para>
         <guilabel>Unnamed Column</guilabel>: Provides a link to the
-        <literal>Close</literal> dialog box
+        <literal>Close</literal> dialog box.
       </para>
     </listitem>
 

@@ -278,31 +279,31 @@
 
     <listitem>
       <para>
-        Severity
+        Severity.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        Date (using a range with From/To)
+        Date (using a range with From/To).
       </para>
     </listitem>
 
     <listitem>
       <para>
-        Advisor group
+        Advisor group.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        Specific rule
+        Specific rule.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        Status
+        Status.
       </para>
     </listitem>
 

@@ -310,14 +311,13 @@
 
   <para>
     Choose the options you are interested in and click the
-    <guibutton>filter</guibutton> button to refresh the display. You may
-    limit the number of items that appear on a page by choosing a
-    different value from the <guilabel>Limit</guilabel> drop down
-    listbox.
+    <guibutton>filter</guibutton> button to refresh the display. To
+    limit the number of items that appear on a page, choose a different
+    value from the <guilabel>Limit</guilabel> dropdown list box.
   </para>
 
   <para>
-    The drop down list box showing severity has the options:
+    The dropdown list box showing severity has the options:
     <literal>All</literal>, <literal>Alerts</literal>,
     <literal>Critical</literal>, <literal>Warning</literal>,
     <literal>Info</literal>, <literal>Success</literal>, and

@@ -344,28 +344,27 @@
   <para>
     The server shown in <xref linkend="mem-events-screen"/>, is filtered
     for <literal>All</literal>. Typically, when filtering by severity
-    you would choose <literal>Alerts</literal> and, if you see a
+    you choose <literal>Alerts</literal> and, if you see a
     <literal>Critical</literal>, <literal>Warning</literal>, or
     <literal>Info</literal> alert, use the <literal>All</literal> filter
-    to see when the rule last ran successfully. This may assist in
-    determining the cause of the alert.
+    to see when the rule last ran successfully. Narrowing down the
+    timeframe can help determine the cause of the alert.
   </para>
 
   <para>
-    Besides filtering for severity, you can also choose to filter for a
-    specific time period using the <literal>From</literal> and
-    <literal>To</literal> text boxes. You also have the choice of
-    filtering by specific rules or categories of rules. The
-    <literal>Status</literal> drop-down list box let's you choose
-    <literal>All</literal>, <literal>Open</literal>, or
+    Besides filtering for severity, you can filter for a specific time
+    period using the <literal>From</literal> and <literal>To</literal>
+    text boxes. You can also filter by specific rules or categories of
+    rules. The <literal>Status</literal> dropdown list box lets you
+    choose <literal>All</literal>, <literal>Open</literal>, or
     <literal>Closed</literal> events. To avoid excessive scrolling, you
-    can also limit the number of events that show on a specific page.
+    can also limit the number of events shown on a specific page.
   </para>
 
   <para>
     For more information about an alert, click the rule name. A pop-up
-    window will appear showing a description of the alert and the exact
-    time of occurrence. This pop-up windows provides links to useful
+    window appears, showing a description of the alert and the exact
+    time of occurrence. This pop-up window provides links to useful
     resources and advice for resolution. You can also view the exact
     expression that generated the event.
   </para>

@@ -375,38 +374,35 @@
     <title>Closing an Event</title>
 
     <para>
-      The creation of an event by an advisor rule signifies that there
-      an issue has been raised which may require closer attention. Once
-      the event has been identified, you should investigate the issue
-      that triggered the event, rectify the issue or problem (or choose
-      to ignore it), and then close the event when you are satisfied
-      that the event is not having a significant impact on your server
-      or servers.
+      The creation of an event by an advisor rule signifies that an
+      issue might require closer attention. Investigate the issue that
+      triggered the event; rectify the issue or problem (or choose to
+      ignore it); then close the event, when you are satisfied it does
+      not have a significant impact on your servers.
     </para>
 
     <para>
-      Some of the advisors are designed to identify issues in your
-      server or &merlin; environment that may either be of a transient
-      nature, or that may indicate a temporary issue (such as a
-      replication slave being unavailable). For these advisors, you can
-      schedule events to automatically be closed when the event moves
-      from notification status back to the <literal>Ok</literal> state.
+      Some of the advisors identify transient or temporary issues, such
+      as a replication slave being unavailable. For these advisors, you
+      can schedule events to automatically be closed when the event
+      moves from notification status back to the <literal>Ok</literal>
+      state.
     </para>
 
     <para>
       You can configure auto-close functionality on all advisors through
       the <guilabel>Advisors</guilabel> tab when you schedule the
       advisor against one or more servers. When auto-close is enabled,
-      the event will remain open while the condition that triggered the
+      the event remains open while the condition that triggered the
       event is still in effect. When the condition is no longer broken,
-      the event will automatically be closed with the configured
-      auto-close test. You can still manually close events that have
-      have been configured with auto-close enabled. For more information
-      on scheduling rules, see <xref linkend="mem-scheduling-rules"/>.
+      the event is automatically closed with the configured auto-close
+      test. You can still manually close such events before resolving
+      the issue. For more information on scheduling rules, see
+      <xref linkend="mem-scheduling-rules"/>.
     </para>
 
     <para>
-      To close an individual alert click the <guilabel>close</guilabel>
+      To close an individual alert, click the <guilabel>close</guilabel>
       link in the <guilabel>Operations/Notes</guilabel> column. Document
       the resolution using the <guilabel>Resolution Notes</guilabel>
       text area and choose the <guibutton>close</guibutton> button.

@@ -418,26 +414,25 @@
 
     <para>
       To close a number of alerts simultaneously, select the checkbox
-      beside each alert that you wish to close and then click the
+      beside each alert to close and click the
       <guibutton>close</guibutton> button.
     </para>
 
     <para>
       When closing individual or multiple events, a notification window
-      will be shown indicating what operations have been completed. The
-      events will remain in the displayed event list, but the
-      <guilabel>close</guilabel> link will instead be a link to the
-      <literal>resolution notes</literal>. You can update the active
-      list by clicking <guibutton>filter</guibutton> to re-filter the
-      event display.
+      indicates what operations have been completed. The events remain
+      in the displayed event list, but the <guilabel>close</guilabel>
+      link is instead a link to the <literal>resolution notes</literal>.
+      You can update the active list by clicking
+      <guibutton>filter</guibutton> to re-filter the event display.
     </para>
 
     <para>
-      An historical list of all events, including closed events, is
-      available by using the <guilabel>Current Severity</guilabel> and
-      setting it to <literal>Closed</literal>. The list will show all of
-      the closed events for a given time range and the servers selected
-      in the server tree.
+      A historical list of all events, including closed events, is
+      available by setting the <guilabel>Current Severity</guilabel> to
+      <literal>Closed</literal>. The list shows all of the closed events
+      for a given time range and the servers selected in the server
+      tree.
     </para>
 
   </section>

@@ -450,7 +445,7 @@
       Notification of an event takes place when a rule is executed and
       the severity level for a given rule changes from a lower status to
       a higher one. This occurs on the first change to each individual
-      severity level until the event has been closed.
+      severity level until the event is closed.
     </para>
 
     <para>

@@ -502,16 +497,15 @@
     </informaltable>
 
     <para>
-      If auto-close has been enabled for a given rule, then the above
-      notification sequence is still valid, but the effect of the
-      auto-close system is that the event will automatically be closed
-      when the event reaches the <literal>Ok</literal> state. This will
-      re-enable notification when the advisor creates a new event.
+      If auto-close is enabled for a given rule, this notification
+      sequence is still valid, but the event is automatically closed
+      when the event reaches the <literal>Ok</literal> state. This
+      re-enables notification when the advisor creates a new event.
     </para>
 
     <para>
       SNMP notifications are sent each time a given rule is executed,
-      irrespective of the current or returned state.
+      regardless of the current or returned state.
     </para>
 
   </section>


Modified: trunk/mysql-monitor-2.2/dashboard-graphs.xml
===================================================================
--- trunk/mysql-monitor-2.2/dashboard-graphs.xml	2011-01-19 18:25:57 UTC (rev 24848)
+++ trunk/mysql-monitor-2.2/dashboard-graphs.xml	2011-01-19 22:34:38 UTC (rev 24849)
Changed blocks: 3, Lines Added: 8, Lines Deleted: 4; 1414 bytes

@@ -9,6 +9,10 @@
 
   <title>The <guilabel>Graphs</guilabel> Tab</title>
 
+  <indexterm>
+    <primary>Graphs tab</primary>
+  </indexterm>
+
   <note>
     <para>
       &commercial_blurb;

@@ -21,7 +25,7 @@
   </para>
 
   <para>
-    By default four graphs are displayed on the <literal>Monitor
+    By default, four graphs are displayed on the <literal>Monitor
     page</literal>. These graphs present information about the currently
     selected server or server group, showing the hit ratios, CPU
     utilization, connections, and database activity. Color coding helps

@@ -50,9 +54,9 @@
     The <guilabel>Graphs</guilabel> tab shows all the available graphs
     and provides the capability of adjusting the scale of the graphs,
     allowing a more or less detailed view as the situation requires. To
-    ensure that you have the latest versions of the various graphs click
-    on the <guilabel>Check For Updates</guilabel> link on the top left
-    of this page.
+    ensure that you have the latest versions of the graphs, click on the
+    <guilabel>Check For Updates</guilabel> link on the top left of this
+    page.
   </para>
 
   <para>


Modified: trunk/mysql-monitor-2.2/dashboard-overview.xml
===================================================================
--- trunk/mysql-monitor-2.2/dashboard-overview.xml	2011-01-19 18:25:57 UTC (rev 24848)
+++ trunk/mysql-monitor-2.2/dashboard-overview.xml	2011-01-19 22:34:38 UTC (rev 24849)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 0; 577 bytes

@@ -9,6 +9,10 @@
 
   <title>Using and Configuring &merlin_client;</title>
 
+  <indexterm>
+    <primary>&merlin_client;</primary>
+  </indexterm>
+
   <para>
     This chapter contains information about the main sections of
     &merlin_client;, how to use the interface, and how to set the


Modified: trunk/mysql-monitor-2.2/dashboard-query-analyzer.xml
===================================================================
--- trunk/mysql-monitor-2.2/dashboard-query-analyzer.xml	2011-01-19 18:25:57 UTC (rev 24848)
+++ trunk/mysql-monitor-2.2/dashboard-query-analyzer.xml	2011-01-19 22:34:38 UTC (rev 24849)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 7; 1338 bytes

@@ -9,14 +9,17 @@
 
   <title>The <guilabel>Query Analyzer</guilabel> Tab</title>
 
+  <indexterm>
+    <primary>Query Analyzer tab</primary>
+  </indexterm>
+
   <para>
-    Query Analyzer lets you monitor the statements being executed
-    on a monitored server and retrieve information about the query,
-    number of executions and the execution times of each query. Queries
-    are normalized, so that the unique data defined within each query
-    has been removed. By removing the data specific elements of the
-    queries, the generic queries can be counted and identified more
-    easily.
+    Query Analyzer lets you monitor the statements being executed on a
+    monitored server and retrieve information about the query, number of
+    executions and the execution times of each query. Queries are
+    normalized, so that the unique data defined within each query has
+    been removed. By removing the data specific elements of the queries,
+    the generic queries can be counted and identified more easily.
   </para>
 
   <para>


Modified: trunk/mysql-monitor-2.2/dashboard-replication.xml
===================================================================
--- trunk/mysql-monitor-2.2/dashboard-replication.xml	2011-01-19 18:25:57 UTC (rev 24848)
+++ trunk/mysql-monitor-2.2/dashboard-replication.xml	2011-01-19 22:34:38 UTC (rev 24849)
Changed blocks: 3, Lines Added: 9, Lines Deleted: 5; 1642 bytes

@@ -9,6 +9,10 @@
 
   <title>The <guilabel>Replication</guilabel> Tab</title>
 
+  <indexterm>
+    <primary>Replication tab</primary>
+  </indexterm>
+
   <note>
     <para>
       &commercial_blurb;

@@ -39,10 +43,10 @@
 
   <para>
     The <literal>Replication</literal> page groups all master servers
-    with their slaves. Masters and their slaves are automatically
-    discovered and a grouping is created. This grouping shows up on the
-    replication page and also in the <guilabel>Heat Chart</guilabel> on
-    the <guilabel>Monitor</guilabel> tab. Scans run on a five minute
+    with their slaves. Masters and their slaves are autodiscovered and a
+    grouping is created. This grouping shows up on the replication page
+    and also in the <guilabel>Heat Chart</guilabel> on the
+    <guilabel>Monitor</guilabel> tab. Scans run on a five minute
     interval, so depending upon the order of discovery, it can take as
     long as 2 polling intervals to create a complete group.
   </para>

@@ -66,7 +70,7 @@
     page and choose the <guilabel>Logs</guilabel> link. View all
     replication-related events by clicking the
     <guilabel>Replication</guilabel> link. This log can be a useful tool
-    should you need to debug the replication topology discovery process.
+    for debugging the replication topology discovery process.
   </para>
 
   <warning>


Modified: trunk/mysql-monitor-2.2/dashboard-settings.xml
===================================================================
--- trunk/mysql-monitor-2.2/dashboard-settings.xml	2011-01-19 18:25:57 UTC (rev 24848)
+++ trunk/mysql-monitor-2.2/dashboard-settings.xml	2011-01-19 22:34:38 UTC (rev 24849)
Changed blocks: 11, Lines Added: 36, Lines Deleted: 14; 4980 bytes

@@ -9,6 +9,10 @@
 
   <title>The <guilabel>Settings</guilabel> Tab</title>
 
+  <indexterm>
+    <primary>Settings tab</primary>
+  </indexterm>
+
   <remark role="dynamic-dependency-list"/>
 
   <note>

@@ -244,8 +248,7 @@
           <para>
             The MIB file supplied with &merlin_server; is not directly
             compatible with OpenNMS. For a sample of the modifications
-            that need to be made, please see the comments for Bug
-            #41714.
+            to make, see the comments for Bug #41714.
           </para>
         </note>
       </listitem>

@@ -312,7 +315,7 @@
           You can alter the hostname and port used to identify the
           &merlin_server; when reporting notifications. This can be
           useful if the server hostname, and the hostname you want to
-          use when connecting to your &merlin_server;
+          use when connecting to your &merlin_server;.
         </para>
 
         <figure id="fig-settings-server-hostname">

@@ -1530,7 +1533,7 @@
     <para>
       The <guilabel>Manage Users</guilabel> panel lets you create,
       delete and manage individual users that have access to
-      &merlin_server;
+      &merlin_server;.
     </para>
 
     <figure id="fig-mem-settings-users">

@@ -1693,13 +1696,13 @@
 
     <para>
       When a new user first logs in, a dialog box opens requesting time
-      zone and locale information. This information may be changed later
-      from the <guilabel>User Preferences</guilabel> tab. For more
+      zone and locale information. To change this information later, use
+      the <guilabel>User Preferences</guilabel> tab. For more
       information, see <xref linkend="mem-user-preferences"/>.
     </para>
 
     <para>
-      If you installed the Advisors through the Dashboard you should
+      If you installed the Advisors through the Dashboard, you should
       have already configured the settings for the root role user. (See
       <xref linkend="mem-global-settings"/> and following for more
       information about this topic.)

@@ -1707,10 +1710,10 @@
 
     <warning>
       <para>
-        To receive &mysql_enterprise; and Advisor updates configure the
+        To receive &mysql_enterprise; and Advisor updates, configure the
         &mysql_enterprise; settings for at least one user. The MySQL
         Enterprise settings were set up on the first login to the
-        Dashboard. For information on changing these settings see,
+        Dashboard. For information on changing these settings, see
         <xref linkend="mem-global-settings"/>.
       </para>
     </warning>

@@ -1833,10 +1836,10 @@
 
     <note>
       <para>
-        You should ensure that there is a mail server available for
-        sending out alerts and that there is an account configured for
-        receiving any alerts that are created. For SMS messages, you
-        must configure an email address with a third-party service that
+        Ensure that there is a mail server available for sending out
+        alerts, and that there is an account configured for receiving
+        any alerts that are created. For SMS messages, you must
+        configure an email address with a third-party service that
         forwards the notification emails to an SMS number. SMS sending
         functionality is not provided in &merlin_server;.
       </para>

@@ -1882,7 +1885,7 @@
 
     <para>
       On this screen you can filter log information in a couple of ways;
-      by the message type and by time period .
+      by the message type and by time period.
     </para>
 
     <para>

@@ -2034,6 +2037,11 @@
           Info</emphasis>
         </para>
 
+        <indexterm>
+          <primary>Java VM</primary>
+          <secondary>version and environment info</secondary>
+        </indexterm>
+
         <para>
           The <guilabel>Enterprise Dashboard Server Info</guilabel>
           section provides detailed information about the running of

@@ -2155,6 +2163,11 @@
           <emphasis role="bold">Diagnostic Report</emphasis>
         </para>
 
+        <indexterm>
+          <primary>Java VM</primary>
+          <secondary>diagnostic report</secondary>
+        </indexterm>
+
         <para>
           The <guilabel>Diagnostic Report</guilabel> section includes a
           hyperlink, <guilabel>Download diagnostic report</guilabel>.

@@ -2177,6 +2190,15 @@
           </listitem>
 
           <listitem>
+            <indexterm>
+              <primary>catalina.out log file</primary>
+            </indexterm>
+
+            <indexterm>
+              <primary>Tomcat</primary>
+              <secondary>catalina.out log file</secondary>
+            </indexterm>
+
             <para>
               <filename>catalina.out</filename>: The Tomcat log file.
             </para>


Modified: trunk/mysql-monitor-2.2/dashboard-whatsnew.xml
===================================================================
--- trunk/mysql-monitor-2.2/dashboard-whatsnew.xml	2011-01-19 18:25:57 UTC (rev 24848)
+++ trunk/mysql-monitor-2.2/dashboard-whatsnew.xml	2011-01-19 22:34:38 UTC (rev 24849)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 0; 588 bytes

@@ -9,6 +9,10 @@
 
   <title>The <guilabel>What's New</guilabel> Tab</title>
 
+  <indexterm>
+    <primary>What's New tab</primary>
+  </indexterm>
+
   <para>
     The What's New Page provides a simplified interface for providing
     updates and news related to your MySQL Enterprise Subscription. By


Thread
svn commit - mysqldoc@docsrva: r24849 - trunk/mysql-monitor-2.2john.russell19 Jan