(DOCSP-32925): Backport DOCSP-32733 to v6.0. (#5203) (#5204)

* (DOCSP-32925): Backport DOCSP-32733 to v6.0. (#5203)

* (DOCSP-32733): Incorporated Frank's feedback.

* (DOCSP-32722): Incorporated Frank's feedback.

* (DOCSP-32733): Fixed typo.

Author: corryroot

source/reference/alerts.txt

@@ -1019,14 +1019,14 @@ WiredTiger storage engine conditions include:
 
 .. include:: /includes/fact-alerts-charting-metrics.rst
 
+.. _system-disk-alerts:
+
 System and Disk Alerts
 ``````````````````````
 
 You may set alerts for compute and disk utilization. System resource
 conditions include:
 
-.. _system-disk-alerts:
-
 .. list-table::
    :widths: 30 70
    :header-rows: 1
@@ -1113,38 +1113,6 @@ conditions include:
        the partition that contains the MongoDB journal exceeds the 
        specified threshold.
 
-   * - Disk I/O % utilization on Data Partition is
-     - Percentage of time during which requests are being issued to
-       any partition that contains the MongoDB collection's data. This
-       includes requests from any process, not just MongoDB processes.
-
-   * - Max disk I/O % utilization on Data Partition is
-     - Maximum percentage of time during which 
-       requests are being issued to any partition that contains the 
-       MongoDB collection's data exceeds the specified threshold.
-
-   * - Disk I/O % utilization on Index Partition is
-     - Percentage of time during which requests are being issued to
-       any partition that contains the MongoDB index data. This
-       includes requests from any process, not just MongoDB processes.
-
-   * - Max disk I/O % utilization on Index Partition is
-     - Maximum percentage of time during which 
-       requests are being issued to any partition that contains the 
-       MongoDB index data exceeds the specified threshold.
-
-   * - Disk I/O % utilization on Journal Partition is
-     - Percentage of time during which requests are being issued to
-       the partition that contains the MongoDB journal, if journaling
-       is enabled. This includes requests from any process, not just
-       MongoDB processes.
-
-   * - Max disk I/O % utilization on Journal Partition is
-     - Maximum percentage of time during which 
-       requests are being issued to the partition that contains the 
-       MongoDB journal exceeds the specified 
-       threshold.
-
    * - System Network In is
      - Number of bytes per second sent *to* the database host meets the
        specified threshold.

source/reference/alerts/disk-io-utilization.txt

@@ -12,52 +12,30 @@ Fix IOPS Issues
    :depth: 1
    :class: singlecol
 
-``Disk I/O % Utilization`` alerts indicate that percentage of time
-during which issued requests reaches a specified threshold. You set
-this threshold when you create the alert.
-
-.. note::
-
-   The utilization measurements for the following alerts include
-   requests from all processes, not just MongoDB processes.
+:ref:`System and disk alert <system-disk-alerts>` conditions can 
+indicate IOPS issues.
 
 Alert Conditions
 ----------------
 
-:ref:`Disk I/O % utilization on Data Partition
-<system-disk-alerts>`
-occurs if the percentage of time during which requests are being
-issued to any partition that contains the MongoDB :term:`collection`
-data meets or exceeds the threshold.
-
-:ref:`Disk I/O % utilization on Index Partition
-<system-disk-alerts>`
-occurs if the percentage of time during which requests are being
-issued to any partition that contains the MongoDB :term:`index`
-data meets or exceeds the threshold.
-
-:ref:`Disk I/O % utilization on Journal Partition
-<system-disk-alerts>`
-occurs if the percentage of time during which requests are being
-issued to the partition that contains the MongoDB
-:term:`journal` meets or exceeds the threshold.
+:alert:`System: CPU (User) % is` measures the CPU usage of the 
+processes on the node, normalized by the number of CPUs. This value is 
+scaled to a range of 0-100%.
 
 Common Triggers
 ---------------
 
-A few common events may lead to high Disk I/O % Utilization and trigger
-these alerts:
+A few common events may trigger these alerts:
 
 - :manual:`Unoptimized queries </core/query-optimization/>`
 
-- A one-time event that spikes disk utilization, such as an
-  :manual:`index build </core/index-creation/>`.
+- A one-time event, such as an :manual:`index build 
+  </core/index-creation/>`.
 
 Fix the Immediate Problem
 -------------------------
 
-Consider the following resolutions to resolve ``Disk I/O %
-Utilization`` alerts:
+Consider the following resolutions:
 
 - :manual:`Optimize your queries </core/query-optimization/>`.
 
@@ -86,7 +64,7 @@ Implement a Long-Term Solution
 Monitor Your Progress
 ---------------------
 
-To observe a high percentage of Disk I/O utilization, open the
+To observe high disk utilization, open the 
 :guilabel:`Hardware Metrics` section of the :guilabel:`Metrics` tab and 
 find the following metrics:
 
@@ -97,8 +75,6 @@ find the following metrics:
 
    * - Graph
      - Indicator
-   * - Util%
-     - High value
    * - Disk IOPS
      - |iops| value greater than the provisioned |iops| value
    * - Normalized System CPU

source/reference/api/measures/get-disk-measurements.txt

@@ -141,11 +141,6 @@ Response Body
          "name": "DISK_PARTITION_IOPS_TOTAL",
          "units": "SCALAR_PER_SECOND"
        },
-       {
-         "dataPoints": [],
-         "name": "DISK_PARTITION_UTILIZATION",
-         "units": "PERCENT"
-       },
        {
          "dataPoints": [],
          "name": "DISK_PARTITION_LATENCY_READ",

source/reference/api/measures/measurement-types.txt

@@ -142,15 +142,6 @@ Disk Measurements
 
        Requires |mms| Automation.
 
-   * - - ``DISK_PARTITION_UTILIZATION``
-       - ``MAX_DISK_PARTITION_UTILIZATION``
-
-     - Percentage of time when the partition issues and services
-       requests. This includes requests from
-       any process, not just MongoDB processes.
-
-       Requires |mms| Automation.
-
    * - - ``DISK_PARTITION_LATENCY_READ``
        - ``MAX_DISK_PARTITION_LATENCY_READ``
        - ``DISK_PARTITION_LATENCY_WRITE``