Merge pull request #2514 from splunk/adasplunk-O11YDOCS-6771

[O11YDOCS-6771] Normalize, alphabetize, deduplicate the "advanced test config" section

Author: adasplunk

index.rst

@@ -758,17 +758,17 @@ To keep up to date with changes in the products, see the Splunk Observability Cl
 .. toctree::
    :maxdepth:   3
 
-   Uptime Tests for port and HTTP TOGGLE <synthetics/uptime-test/uptime-test>
+   Uptime tests for port and HTTP TOGGLE <synthetics/uptime-test/uptime-test>
 
 .. toctree::
    :maxdepth:   3
 
-   Use an API test to test an endpoint TOGGLE <synthetics/api-test/api-test>
+   API tests for endpoints TOGGLE <synthetics/api-test/api-test>
 
 .. toctree::
    :maxdepth:   3
 
-   synthetics/test-kpis/test-kpis
+   Test status TOGGLE <synthetics/test-status/test-status>
 
 .. toctree::
    :maxdepth:   3

synthetics/api-test/api-test.rst

@@ -1,7 +1,7 @@
 .. _api-test:
 
 ************************************
-API Tests for endpoint
+API tests for endpoints
 ************************************
 
 .. meta::

synthetics/test-config/built-in-variables.rst

@@ -1,7 +1,7 @@
 .. _built-in-variables:
 
 ***********************************
-Built-in variables to use in tests
+Built-in variables
 ***********************************
 
 .. meta::

synthetics/test-config/devices.rst

@@ -0,0 +1,26 @@
+.. _devices:
+
+*****************************************
+Devices 
+*****************************************
+
+.. meta::
+    :description: Select a predefined device to simulate a specific viewport size and network connection for a test.
+
+When you set up a test in Splunk Synthetic Monitoring, you can select a predefined device to simulate a specific viewport size and network connection for that test. Every predefined device is a combination of a specific viewport size and network connection. 
+
+* A viewport is the framed area on a device's screen for viewing information, such as the browser window on a desktop. Since a viewport is an integral part of the visual experience of a user interacting with your application or site, viewport settings only apply to visual tests (browser tests). Viewport settings don't apply to API or uptime tests, because these tests are non-visual -- they only capture response data from your application or site.
+* A network connection is the network type, speed, bandwidth, and latency experienced by a device. Since a network connection is an integral part of all experiences, network connection settings apply to all test types. Testing your site or application from a variety of network connections helps you to monitor the experience of users in a variety of environments.
+
+
+Select a device type for Splunk Synthetic Monitoring tests
+==========================================================
+
+All tests have the device type :guilabel:`Default Desktop` by default. To change this for any test, follow these steps:
+
+#. From the landing page of Splunk Observability Cloud, navigate to Splunk Synthetic Monitoring.
+#. Select the test that you want to change.
+#. Select :guilabel:`Edit test`. The test creation view opens.
+#. In the :guilabel:`Device` field, select one of the predefined devices.
+#. Select :guilabel:`Save`. 
+

synthetics/test-config/global-variables.rst

@@ -1,13 +1,13 @@
 .. _global-variables:
 
 *****************************************
-Create and use global variables 
+Global variables 
 *****************************************
 
 .. meta::
     :description: Define a variable that you can use in multiple browser and API tests in Splunk Synthetic Monitoring.
 
-Define a global variable once, and then use it across all of your browser and API tests.
+Global variables are pre-saved, reusable variables that you define once and use across all your browser and API tests. 
 
 
 How can you use a global variable?

synthetics/test-config/private-locations.rst

@@ -5,7 +5,7 @@ Private locations
 *****************
 
 .. meta::
-    :description: Run synthetic tests from an internal site or private web application to quickly find defects using Splunk Synthetic Monitoring. 
+    :description: Run synthetic tests from private locations such as internal sites, private web applications, or private networks.
 
 A private location is a software package that offers a quick and easy deployment of Splunk Synthetic Monitoring solutions beyond the public network so that you can find, fix, and prevent web performance defects on any internal web application, in any environment - whether inside or outside of your firewalls. Private locations allow Splunk Synthetics Monitoring users to test sooner in the development cycle and against internal sites or applications that aren't available to the public.
 

synthetics/test-config/public-locations.rst

@@ -5,7 +5,7 @@ Public locations
 *****************
 
 .. meta::
-    :description: Run synthetic tests from locations set by infrastructure and connectivity providers to simulate performance for users in that location.
+    :description: Run synthetic tests from locations set by infrastructure and connectivity providers to simulate performance from a range of checkpoints around the world.
 
 Public locations are global checkpoints from which you can run synthetic tests to simulate performance for users in that location.
 

synthetics/test-config/syn-downtimes.rst

@@ -1,7 +1,7 @@
 .. _syn-downtimes:
 
 ************************************************************
-Schedule a downtime configuration
+Downtime
 ************************************************************
 
 

synthetics/test-config/synth-alerts.rst

@@ -1,7 +1,7 @@
 .. _synth-alerts:
 
 ************************************************************
-Set up detectors and alerts in Splunk Synthetic Monitoring
+Detectors and alerts
 ************************************************************
 
 .. meta::

synthetics/test-config/test-config.rst

@@ -9,92 +9,19 @@ Advanced test configurations
 
 .. toctree::
 
-   synth-alerts
    built-in-variables
+   synth-alerts
+   devices
+   syn-downtimes
    global-variables
-   public-locations
    private-locations
+   public-locations
    rum-synth
    try-now
-   syn-downtimes
+   
 
 To simulate diverse types of traffic to your site or application, use a range of configuration options to customize each of your tests.
 
-========================================================================================
-Devices
-========================================================================================
-
-When you set up a test in Splunk Synthetic Monitoring, you can configure the viewport and network connection of the device from which the test is simulated. 
-
-Because Browser tests capture the visual experience of a page, while Uptime and API tests only capture response data, viewport applies to Browser tests only. Network connection applies to all test types. 
-
-----------------------------------------------------------------------------------------
-Viewport
-----------------------------------------------------------------------------------------
-Browser tests in Splunk Synthetic Monitoring capture the visual experience of a user interacting with your application. The viewport is the framed area on a device's screen for viewing information, such as the browser window on a desktop. By default, Browser tests run from a desktop-sized viewport. You can configure tests to run from other viewport sizes to test the user experience from a variety of window sizes and device types. 
-
-When you set up a test, you can choose the viewport size from a list of common devices, or set a custom viewport by height and width. 
-
-----------------------------------------------------------------------------------------
-Network connection
-----------------------------------------------------------------------------------------
-You can run Browser, Uptime, or API tests to simulate network connections of various latencies, including Mobile LTE, Mobile 3G, DSL, Mobile 5G, and cable internet. Testing your site from a variety of connection types lets you monitor the experience of users in a variety of settings. 
-
-========================================================================================
-Variables
-========================================================================================
-Use variables to fill in fields, provide URLs, and enter other information during your tests. 
-
-.. list-table::
-   :header-rows: 1
-   :widths: 20 80 
-
-   * - :strong:`Variable type`
-     - :strong:`Description`
-   * - Built-in variables 
-     - Built-in variables such as random values, dates and times, or location names, for use in your Browser and API Tests. See :ref:`built-in-variables` to learn more.  
-   * - Global variables 
-     - Pre-saved, reusable variables you can define once and use across all your Browser and API tests. See :ref:`global-variables` to learn more. 
-
-========================================================================================
-Locations
-========================================================================================
-Specify locations for your tests to simulate traffic from a range of checkpoints around the world, or use private locations to test sites from within a private network.
-
-For more, see: 
-
-* :ref:`public-locations` 
-* :ref:`private-locations`
-
-.. * See :ref:`private-locations` to set up private locations. 
-
-
-========================================================================================
-Test state and current status
-========================================================================================
-You can use the play and pause buttons in the more menu (|more|) of your tests to pause or resume data collection. 
-
-The current status of a test is updated every time you load the :guilabel:`Test Overview` page in Splunk Synthetic Monitoring. The following table describes the possible status types for each test. 
-
-.. list-table::
-   :header-rows: 1
-   :widths: 20, 80
-
-   * - :strong:`Current status`
-     - :strong:`Description`
-
-   * - Pending
-     - Splunk Synthetic Monitoring is still retrieving the status of this test. 
-
-   * - Available
-     - The test is functioning properly. If the test is active, data is being collected at the set interval and can be viewed in the :guilabel:`Test History` page. If the test is paused, it can be unpaused and will resume collecting data.
-
-   * - No Data 
-     - The test isn't currently collecting data. 
-
-   * - Failure
-     - The test encountered a failure. 
-
 ========================================================================================
 Test naming conventions
 ========================================================================================
@@ -106,22 +33,6 @@ Choosing informative names for your tests and alerts helps organize content. Her
 
 .. image:: /_images/synthetics/ButtercupGames-naming-convention.png
       :width: 60%
-      :alt: This image shows two Browser tests with the prefix [ButtercupGames].
-
-
-================================
-Troubleshoot broken tests 
-================================
-
-See, :ref:`syn-troubleshoot`.
+      :alt: This image shows two browser tests with the prefix [ButtercupGames].
 
 
-
-========================================================================================
-Filter tests
-========================================================================================
-You can filter by test type, key-value pairs, and more. 
-
-.. image:: /_images/synthetics/syn-filter-test.png
-      :width: 60%
-      :alt: This image shows the filter env:prod for all tests on the Synthetic homepage..