Revert unneeded changes in scenarios files

Author: pauljwil

alerts-detectors-notifications/alerts-and-detectors/scenarios-detectors-alerts/find-detectors.rst

@@ -1,69 +1,69 @@
-.. _find-detectors:
-
-*************************************************************
-Scenario: Kai finds active alerts to investigate a CPU issue
-*************************************************************
-
-
-
-.. meta::
-    :description: This Splunk alerts and detectors scenario describes how to find active alerts.
-
-Kai, a site reliability engineer at Buttercup Games, has created a detector called "CPU Detector" that monitors Buttercup Games host machine's CPU usage for sudden changes. Kai has received many alerts from this detector, and wants to get a more detailed view of these alerts. 
-
-Using the :guilabel:`Alerts & Detectors` page in Splunk Observability Cloud, Kai can find and view these active alerts so they can easily troubleshoot the CPU changes.
-
-Find active alerts using the search list
-====================================================
-
-From the :guilabel:`Alerts & Detectors` page, Kai can find active alerts using the search list. Kai follows these steps: 
-
-#. Kai wants to find an active alert, so they select the :guilabel:`Active Alerts` tab.
-#. Kai enters filters so they can find their active alerts more easily. They enter desired values for the following fields:
-
-.. list-table::
-    :header-rows: 1
-    :widths: 33 33 33
-
-    * - Field
-      - Value 
-      - Description 
-
-    * - :guilabel:`Group By`
-      - :guilabel:`host.name`
-      - Groups active alerts from the same host machine name into one category.
-
-    * - :guilabel:`Team`
-      - :guilabel:`Buttercup Games` 
-      - Shows only active alerts from detectors created by the Buttercup Games team.
-
-After applying filters, Kai finds a list of active alerts triggered by their detector:
-
-.. image:: /_images/images-detectors-alerts/use-cases/active-alerts-list.png
-    :width: 100%
-    :alt: This screenshot shows a list of active alerts.
-
-View details of active alerts
-===================================================
-
-Now that Kai has found their active alerts in the search list, Kai wants to see which alerts are active for this detector.
-
-Kai can now view a detailed report of each active alert associated with their detector by selecting the alert name. 
-
-.. image:: /_images/images-detectors-alerts/use-cases/detail-view-cpu.png
-    :width: 100%
-    :alt: This screenshot shows a detailed view of one of the alerts, displaying a spike in CPU value. 
-
-By viewing several of these alerts, Kai determines that one of their host machines experienced spikes in CPU utilization. 
-
-Summary
-=======================
-
-Kai viewed a list of active alerts triggered by their detector. By finding and viewing the detailed reports of these active alerts, Kai discovered that one of their host machines experienced sudden increases in CPU usage, and they can now troubleshoot the problem more easily.
-
-Learn more
-=======================
-
-For more information about ways to view alerts, see :ref:`view-alerts`. 
-
-For more information about ways to view detectors, see :ref:`view-detectors`.
+.. _find-detectors:
+
+*************************************************************
+Scenario: Kai finds active alerts to investigate a CPU issue
+*************************************************************
+
+
+
+.. meta::
+    :description: This Splunk alerts and detectors scenario describes how to find active alerts.
+
+Kai, a site reliability engineer at Buttercup Games, has created a detector called "CPU Detector" that monitors Buttercup Games host machine's CPU usage for sudden changes. Kai has received many alerts from this detector, and wants to get a more detailed view of these alerts. 
+
+Using the :guilabel:`Alerts & Detectors` page in Splunk Observability Cloud, Kai can find and view these active alerts so they can easily troubleshoot the CPU changes.
+
+Find active alerts using the search list
+====================================================
+
+From the :guilabel:`Alerts & Detectors` page, Kai can find active alerts using the search list. Kai follows these steps: 
+
+#. Kai wants to find an active alert, so they select the :guilabel:`Active Alerts` tab.
+#. Kai enters filters so they can find their active alerts more easily. They enter desired values for the following fields:
+
+.. list-table::
+    :header-rows: 1
+    :widths: 33 33 33
+
+    * - Field
+      - Value 
+      - Description 
+
+    * - :guilabel:`Group By`
+      - :guilabel:`host.name`
+      - Groups active alerts from the same host machine name into one category.
+
+    * - :guilabel:`Team`
+      - :guilabel:`Buttercup Games` 
+      - Shows only active alerts from detectors created by the Buttercup Games team.
+
+After applying filters, Kai finds a list of active alerts triggered by their detector:
+
+.. image:: /_images/images-detectors-alerts/use-cases/active-alerts-list.png
+    :width: 100%
+    :alt: This screenshot shows a list of active alerts.
+
+View details of active alerts
+===================================================
+
+Now that Kai has found their active alerts in the search list, Kai wants to see which alerts are active for this detector.
+
+Kai can now view a detailed report of each active alert associated with their detector by selecting the alert name. 
+
+.. image:: /_images/images-detectors-alerts/use-cases/detail-view-cpu.png
+    :width: 100%
+    :alt: This screenshot shows a detailed view of one of the alerts, displaying a spike in CPU value. 
+
+By viewing several of these alerts, Kai determines that one of their host machines experienced spikes in CPU utilization. 
+
+Summary
+=======================
+
+Kai viewed a list of active alerts triggered by their detector. By finding and viewing the detailed reports of these active alerts, Kai discovered that one of their host machines experienced sudden increases in CPU usage, and they can now troubleshoot the problem more easily.
+
+Learn more
+=======================
+
+For more information about ways to view alerts, see :ref:`view-alerts`. 
+
+For more information about ways to view detectors, see :ref:`view-detectors`.

alerts-detectors-notifications/alerts-and-detectors/scenarios-detectors-alerts/monitor-autodetect.rst

@@ -1,76 +1,76 @@
-.. _monitor-autodetect:
-
-****************************************************
-Scenario: Kai monitors system limits with AutoDetect 
-****************************************************
-
-
-
-.. meta::
-    :description: This Splunk alerts and detectors scenario describes how to use AutoDetect to track system limits.
-
-Kai, a site reliability engineer at Buttercup Games, wants to know when they are reaching their limit for the number of detectors they can create for Buttercup Games. This limit is automatically monitored through an AutoDetect detector, which Kai can view from the Alerts and Detectors page.
-
-View AutoDetect alerts and detectors
-========================================
-
-To use their AutoDetect detector, Kai must first find and view the details of the detector. The name of the detector is :guilabel:`Splunk Operational -- Number of detectors is expected to reach the maximum`.
-
-Kai finds the detector by following these steps:
-
-#. Kai opens the :guilabel:`All alerts` menu and unchecks :strong:`Standard` and :strong:`Customized AutoDetect` to filter for only AutoDetect detectors.
-#. Kai enters the name of the detector in the search bar.
-#. Kai selects the detector from the result list.
-
-.. image:: /_images/images-detectors-alerts/use-cases/autodetect-search.png
-    :width: 100%
-    :alt: This screenshot shows the detectors search list with Kai's detector appearing as the first search result.
-
-After Kai finds the AutoDetect detector that monitors the maximum number of detectors for Buttercup Games, they can set up alerts and add a preferred notification channel.
-
-Subscribe to AutoDetect detectors
-=========================================
-
-Kai wants to be alerted whenever their AutoDetect detector triggers an alert indicating that Buttercup Games has almost reached their maximum number of detectors. Kai can receive an alert from the system limits detector by subscribing to the detector. 
-
-To subscribe to an AutoDetect detector, Kai follows these steps:
-
-#. Kai finds their AutoDetect detector from the search list or their integration.
-#. Kai selects :guilabel:`Add Recipients`.
-#. Kai sets up the notification channel of their choice.
-
-Kai will receive a notification whenever their AutoDetect detector triggers an alert for maximum number of detectors created.
-
-Disable AutoDetect detectors
-=========================================
-
-Kai decides that they no longer want to use their AutoDetect detector, as Buttercup Games has not come close to reaching their system limit. In this case, Kai can disable the detector by following these steps:
-
-#. Kai finds their detector from the search list.
-#. Kai selects :guilabel:`Disable Detector`. This stops the detector from reporting on data and Kai no longer receives notifications from the detector.
-
-Customize AutoDetect detectors
-=================================
-
-Kai's AutoDetect detector will trigger an alert when the number of detectors used is 90%, but Kai would like to be alerted when they are reaching 75% of the detectors used instead. To receive these alerts, Kai can customize the system limits AutoDetect detector.
-
-To customize this detector, Kai follows these steps:
-
-#. Kai selects the :guilabel:`Splunk Operational -- Number of detectors is expected to reach the maximum` detector. 
-#. In the detector menu, Kai selects :guilabel:`Create a Customized Version`.
-#. Kai changes the :guilabel:`Trigger threshold` to :guilabel:`75%`.
-#. Kai selects :guilabel:`Activate`. 
-
-Kai has created a new AutoDetect detector that will alert them whenever the number of detectors used reaches 75%. 
-
-Summary
-=====================
-
-In this scenario, Kai set up and subscribed to an AutoDetect detector that reported on system limits for Buttercup Games. Kai also learned how to find, disable, and customize the AutoDetect detector.
-
-Learn more
-=========================================
-
-For more information about AutoDetect detectors, see :ref:`autodetect`. 
-
-For information about AutoDetect integrations and types of AutoDetect detectors, see :ref:`autodetect-list`
+.. _monitor-autodetect:
+
+****************************************************
+Scenario: Kai monitors system limits with AutoDetect 
+****************************************************
+
+
+
+.. meta::
+    :description: This Splunk alerts and detectors scenario describes how to use AutoDetect to track system limits.
+
+Kai, a site reliability engineer at Buttercup Games, wants to know when they are reaching their limit for the number of detectors they can create for Buttercup Games. This limit is automatically monitored through an AutoDetect detector, which Kai can view from the Alerts and Detectors page.
+
+View AutoDetect alerts and detectors
+========================================
+
+To use their AutoDetect detector, Kai must first find and view the details of the detector. The name of the detector is :guilabel:`Splunk Operational -- Number of detectors is expected to reach the maximum`.
+
+Kai finds the detector by following these steps:
+
+#. Kai opens the :guilabel:`All alerts` menu and unchecks :strong:`Standard` and :strong:`Customized AutoDetect` to filter for only AutoDetect detectors.
+#. Kai enters the name of the detector in the search bar.
+#. Kai selects the detector from the result list.
+
+.. image:: /_images/images-detectors-alerts/use-cases/autodetect-search.png
+    :width: 100%
+    :alt: This screenshot shows the detectors search list with Kai's detector appearing as the first search result.
+
+After Kai finds the AutoDetect detector that monitors the maximum number of detectors for Buttercup Games, they can set up alerts and add a preferred notification channel.
+
+Subscribe to AutoDetect detectors
+=========================================
+
+Kai wants to be alerted whenever their AutoDetect detector triggers an alert indicating that Buttercup Games has almost reached their maximum number of detectors. Kai can receive an alert from the system limits detector by subscribing to the detector. 
+
+To subscribe to an AutoDetect detector, Kai follows these steps:
+
+#. Kai finds their AutoDetect detector from the search list or their integration.
+#. Kai selects :guilabel:`Add Recipients`.
+#. Kai sets up the notification channel of their choice.
+
+Kai will receive a notification whenever their AutoDetect detector triggers an alert for maximum number of detectors created.
+
+Disable AutoDetect detectors
+=========================================
+
+Kai decides that they no longer want to use their AutoDetect detector, as Buttercup Games has not come close to reaching their system limit. In this case, Kai can disable the detector by following these steps:
+
+#. Kai finds their detector from the search list.
+#. Kai selects :guilabel:`Disable Detector`. This stops the detector from reporting on data and Kai no longer receives notifications from the detector.
+
+Customize AutoDetect detectors
+=================================
+
+Kai's AutoDetect detector will trigger an alert when the number of detectors used is 90%, but Kai would like to be alerted when they are reaching 75% of the detectors used instead. To receive these alerts, Kai can customize the system limits AutoDetect detector.
+
+To customize this detector, Kai follows these steps:
+
+#. Kai selects the :guilabel:`Splunk Operational -- Number of detectors is expected to reach the maximum` detector. 
+#. In the detector menu, Kai selects :guilabel:`Create a Customized Version`.
+#. Kai changes the :guilabel:`Trigger threshold` to :guilabel:`75%`.
+#. Kai selects :guilabel:`Activate`. 
+
+Kai has created a new AutoDetect detector that will alert them whenever the number of detectors used reaches 75%. 
+
+Summary
+=====================
+
+In this scenario, Kai set up and subscribed to an AutoDetect detector that reported on system limits for Buttercup Games. Kai also learned how to find, disable, and customize the AutoDetect detector.
+
+Learn more
+=========================================
+
+For more information about AutoDetect detectors, see :ref:`autodetect`. 
+
+For information about AutoDetect integrations and types of AutoDetect detectors, see :ref:`autodetect-list`