Misc fixes

Author: ada

private-preview/aopt/aopt-derived-metrics.rst

@@ -13,7 +13,8 @@ Application Optimization's workload analysis produces the following metics. All
 
 All metric names are constructed as ``<prefix>.<section>.<metric>``, where ``<prefix>`` is a prefix (likely either ``sf`` or ``o11y``), and ``<section>`` and ``<metric>`` correspond to columns in the table below.
 
-Note: memory is specified in GiB.
+.. note::
+    Memory is specified in GiB.
 
 
 
@@ -30,7 +31,7 @@ Note: memory is specified in GiB.
       - **Notes**
    - 
 
-      - report
+      - ``report``
       - 
       - 
       - 
@@ -55,7 +56,7 @@ Note: memory is specified in GiB.
       - ``coverage_ratio``
       - W
       - Window coverage with metrics: the ratio of number of actual metrics values found compared to the number of timeslots in the window. This should represent the worst case value (in other words, the minimum of the coverage of each input timeseries we use).
-      - This is used to determine the validity & confidence level of the report.
+      - This is used to determine the validity and confidence level of the report.
    - 
 
       - 
@@ -423,7 +424,7 @@ The following additional dimensions are applied to per-container metrics (any me
 
       - ``k8s.container.pseudo_qos``
       - Container-level pseudo-QoS
-      - to be considered, probably doesn't exist in the input metrics
+      - 
 
 Note: this set of additional attributes matches the set of additional attributes that per-container ``k8s`` metrics (such as memory and CPU utilization), provide on top of workload-level metrics (such as replica count). This excludes metadata attributes that are per pod instance (such ``as k8s.replica.set`` and ``k8s.pod.id``, since we always aggregate
 metrics across instances), as well as per container instance (such as ``k8s.container.id``) for the same reason.

private-preview/aopt/aopt-intro.rst

@@ -29,7 +29,7 @@ Requirements
 
 * Supported Kubernetes workload kinds: Deployment, StatefulSet, DaemonSet
 
-* Minimum amount of infrastructure metrics you must send to Splunk IM: 14 contiguous days. Minimum amount of infrastructure metrics you must send to Splunk IM: 14 contiguous days. This isn't strictly a requirement because instant recommendationss are still generated for less data, but with lower confidence scores
+* Minimum amount of infrastructure metrics you must send to Splunk IM: 14 contiguous days. This isn't strictly a requirement because instant recommendationss are still generated for less data, but with lower confidence scores
 
 * All metrics that the :new-page:`Splunk IM Kubernetes cluster receiver collects by default <https://docs.splunk.com/observability/en/gdi/opentelemetry/collector-kubernetes/install-k8s.html#helm-chart-supported-distros>` must be present in your data. Since these metrics are enabled by default on your Kubernetes collector you don't need to take any action unless you've disabled them. 
 

private-preview/aopt/aopt-scenarios.rst

@@ -39,10 +39,10 @@ To see actual usage metrics for an individual workload:
 
 #. Navigate to the :guilabel:`Application Optimization` dashboard.
 
-#. Find the target workload in the :guilabel:`Kubernetes Workloads` table. :ref:`Sort, search, or filter this table <aopt-workloads>` as needed.  
+#. Find the target workload in the :guilabel:`Kubernetes Workloads` table. :ref:`Sort, search, or filter this table <aopt-workloads-sort-search>` as needed.  
 
-#. Select the target workload in the table to navigate to the :guilabel:`Workloads Details` page. This page displays actual usage metrics for the target workload.
+#. Select the target workload in the table to navigate to the :guilabel:`Workloads Details` page. This page displays actual usage metrics for the target workload, divided into sections for each container in the workload.
 
-#. In the :guilabel:`Instant Recommendations` section, copy the YAML snippets in the far right column and apply them to the corresponding containers in your workload.
+#. In the :guilabel:`Instant Recommendations` section, expand each container's section and apply the YAML snippets in the rightmost column to that container's configuration.
 
 

private-preview/aopt/aopt-workload-details.rst

@@ -22,15 +22,15 @@ Efficiency Analysis
 
 :guilabel:`Efficiency Analysis` is based on the workload's resource efficiency.
 
-* :guilabel:`Confidence level`: Look for the confidence level under the Efficiency Analysis label. If the confidence level is something other than high, this probably means that your cluster hasn't sent enough metrics to Splunk IM since you created the workload. In this case, for highly critical business workflows or those that have high variations, wait a few days for the confidence level to increase before you apply the recommendations. :ref:`See details on how this is calculated <aopt-glossary>`.
+* :guilabel:`Confidence level`: Look for the confidence level under the :guilabel:`Efficiency Analysis` label. If the confidence level is something other than high, this probably means that your cluster hasn't sent enough metrics to Splunk IM since you created the workload. In this case, for highly critical business workflows or those that have high variations, wait a few days for the confidence level to increase before you apply the recommendations. :ref:`See details on how this is calculated <aopt-glossary-confidence-level>`.
 
 * :guilabel:`Resource Starvation Risk`: This workload's average risk of running out of CPU or memory.
 
 * :guilabel:`Average Pod Count`: The number of pods (:new-page:`replicas <https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/>`) running for this workload averaged over the analysis period. 
 
 * :guilabel:`Resource Footprint`: The percentage of CPU and memory that this workload's pods requested, averaged over the analysis period. The footprint may exceed 100% when the pods use more than their requested values.
 
-* :guilabel:`Resource Efficiency`: The ratio of resource usage to resource allocation. This is a percentage relative to allocated resources. The higher the percentage, the better. :ref:`See details on how this is calculated <aopt-glossary>`.
+* :guilabel:`Resource Efficiency`: The ratio of resource usage to resource allocation. This is a percentage relative to allocated resources. The higher the percentage, the better. :ref:`See details on how this is calculated <aopt-glossary-efficiency>`.
 
 
 Instant Recommendations
@@ -48,7 +48,7 @@ If a workload has had a medium or high starvation risk over the past 14 days, ig
 Workload Breakdown
 ==========================================================
 
-Your workload is broken down into its containers, and within the section for each container, there are specific recommendations for CPU and memory adjustments, a chart visualizing its historical resource usage, and on the far right, YAML snippets you can copy to improve its settings. 
+Your workload is broken down into its containers, and within the section for each container, there are specific recommendations for CPU and memory adjustments, a chart visualizing its historical resource usage, and in the rightmost column (:guilabel:`Recommended K8s Spec`), YAML snippets you can copy to improve its settings. 
 
 
 HPA Recommendation

private-preview/aopt/aopt-workloads.rst

@@ -37,7 +37,7 @@ Workloads
 Workloads by Starvation Risk
 ==========================================================
 
-This is a good tile to check first to see if any of your workloads are at high risk of starvation. Those are the workloads that need immediate attention. You can also find starving workloads by sorting the :guilabel:`Kubernetes Workloads` table by :guilabel:`Starvation Risk`. :ref:`See details on how this risk is calculated <aopt-glossary>`.
+This is a good tile to check first to see if any of your workloads are at high risk of starvation. Those are the workloads that need immediate attention. You can also find starving workloads by sorting the :guilabel:`Kubernetes Workloads` table by :guilabel:`Starvation Risk`. :ref:`See details on how this risk is calculated <aaopt-glossary-starvation-risk>`.
 
 
 Resource Footprint
@@ -49,6 +49,8 @@ A workload's resource footprint is the sum of its pods' ``request`` settings for
     This tile aggregates data from all of your workloads, so you may not find a direct correlation to individual workloads in the :guilabel:`Kubernetes Workloads` table.
 
 
+.. _aopt-workloads-sort-search:
+
 Kubernetes Workloads
 ==========================================================
 

private-preview/aopt/toc.rst

@@ -16,9 +16,10 @@
 .. admonition:: Table of contents
 
     Use these links to navigate to topics within this private preview: 
-        * :ref:`What is Application Optimization <aopt-intro>`
+        * :ref:`What is Application Optimization? <aopt-intro>`
         * :ref:`The Application Optimization dashboard <aopt-workloads>`
         * :ref:`Workload Details <aopt-workload-details>`
         * :ref:`Scenarios <aopt-scenarios>`
-        * :ref:`Derived metrics <aopt-derived-metrics>`
         * :ref:`Glossary <aopt-glossary>`
+        * :ref:`Derived metrics <aopt-derived-metrics>`
+