Pulling refs/heads/main into main

admin/notif-services/servicenow.rst

@@ -44,7 +44,7 @@ Before you set up the integration, choose a ServiceNow issue type from the follo
         - ``user_admin``, ``itil``
         - ``/api/now/v2/table/incident``
       * - Event
-        - None
+        - ``evt_mgmt_integration``, only if :guilabel:`Requires ACL authorization` is selected for :strong:`Inbound Event Default Bulk Endpoint` in :strong:`Scripted Rest APIs`. To learn more, see the :new-page:`ServiceNow support article on events <https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0993277>`.
         - ``/api/global/em/jsonv2``
 
 Make note of the role and receiving endpoint that corresponds to your issue type before proceeding with :ref:`servicenow2`.
@@ -112,9 +112,9 @@ To create a ServiceNow integration in Splunk Observability Cloud:
 
    To troubleshoot potential blind server-side request forgeries (SSRF), Splunk Observability Cloud has included ``\*.service-now.com`` on an allow list. As a result, if you enter a domain name that is rejected by Splunk Observability Cloud, contact :ref:`support` to update the allow list of domain names.
 
-#. Select :strong:`Incident`, :strong:`Problem`, or :strong:`Event` to indicate the issue type you want the integration to create in ServiceNow. If necessary, you can create a second integration using the other issue type. This lets you create an incident issue for one detector rule and a problem issue for another detector rule. The following table shows the roles required to create each issue type:
+#. Select :strong:`Incident`, :strong:`Problem`, or :strong:`Event` to indicate the issue type you want the integration to create in ServiceNow. If necessary, you can create a second integration using another issue type. This lets you create an incident issue for one detector rule and a problem issue for another detector rule.
 
-#. :strong:`Save`.
+#. Select :strong:`Save`.
 
 #. If Splunk Observability Cloud can validate the ServiceNow username, password, and instance name combination, a :strong:`Validated!` success message displays. If an error displays instead, make sure that the values you entered match the values in ServiceNow.
 

index.rst

@@ -843,7 +843,18 @@ To keep up to date with changes in the products, see the Splunk Observability Cl
 .. toctree::
    :maxdepth:   3
 
-   Configure your tests TOGGLE <synthetics/test-config/test-config>
+   Advanced test configurations TOGGLE <synthetics/test-config/test-config>
+
+.. toctree::
+   :maxdepth:   3
+
+   Troubleshoot tests TOGGLE <synthetics/syn-troubleshoot/syn-troubleshoot>
+
+
+.. toctree::
+   :maxdepth:   3
+
+   Troubleshoot tests  <synthetics/syn-troubleshoot/syn-missing-alerts>
 
 .. toctree::
    :caption: Splunk On-Call

release-notes/2024-10-01-rn.rst

@@ -66,4 +66,19 @@ Service level objective (SLO)
    * - New feature or enhancement
      - Description
    * - SignalFlow editor for custom metrics SLO
-     - You can use SignalFlow to define metrics and filters when creating a custom metric SLO. For more information, see :ref:`create-slo`. The feature released on October 2, 2024.
+     - You can use SignalFlow to define metrics and filters when creating a custom metric SLO. For more information, see :ref:`create-slo`. The feature released on October 2, 2024.
+
+.. _auth-2024-10-01:
+
+Authentication
+==============
+
+.. list-table::
+   :header-rows: 1
+   :widths: 1 2
+   :width: 100%
+
+   * - New feature or enhancement
+     - Description
+   * - Token management improvements
+     - Admin and power users have a new token management interface that includes long-lived tokens, improved token visibility and rotation, and a design that is aligned with Splunk Cloud Platform. For more information, see :ref:`admin-org-tokens`. The feature released on October 23, 2024.

release-notes/release-notes-overview.rst

@@ -32,6 +32,7 @@ Each release date includes new features and enhancements for SaaS and versioned
        * :ref:`Data ingest <ingest-2024-20-01>`
        * :ref:`Data management <data-mngt-2024-10-01>`
        * :ref:`Service level objective <slo-2024-10-01>`
+       * :ref:`Token management improvements <auth-2024-10-01>`
 
 .. _changelogs:
 

synthetics/api-test/api-test.rst

@@ -1,7 +1,7 @@
 .. _api-test:
 
 ************************************
-Use an API Test to test an endpoint
+API Tests for endpoint
 ************************************
 
 .. meta::

synthetics/browser-test/browser-test-results.rst

@@ -1,7 +1,7 @@
 .. _browser-test-results:
 
 ***********************************************
-Interpret Browser Test results
+Interpret Browser test results
 ***********************************************
 
 .. meta::

synthetics/browser-test/browser-test.rst

@@ -1,7 +1,7 @@
 .. _browser-test:
 
 ****************************************
-Use a Browser test to test a webpage
+Browser tests for webpages
 ****************************************
 
 .. meta::
@@ -21,7 +21,7 @@ You can configure tests on a schedule so you're continually monitoring your site
 .. raw:: html
 
   <embed>
-    <h2>What happens during a Browser test?</h2>
+    <h2>What does a Browser test monitor?</h2>
   </embed>
 
 During a Browser test, Splunk Synthetic Monitoring continuously collects performance data including metrics, network data, and custom user timings. All requests and responses that occur in the test are captured in a HAR file, which is represented visually in a waterfall chart that illustrates the latency of specific resources on the page. See :ref:`waterfall-chart` to learn more about the waterfall chart, and see :ref:`browser-metrics` to learn about the metrics in a Browser test.

synthetics/set-up-synthetics/set-up-synthetics.rst

@@ -11,6 +11,30 @@ Set up Splunk Synthetic Monitoring
 
 Monitor the performance of your web pages and applications by running synthetic Browser, Uptime, and API tests. These tests let you proactively alert the relevant teams when a site or user flow they manage becomes unavailable, as well as report on the performance of a site or user flow over time. Splunk Synthetic Monitoring does not require extensive installation and setup: you can get started by creating your first test directly in the Splunk Synthetic Monitoring user interface. 
 
+.. _synth-configure-app:
+
+Get your site ready to run synthetic tests
+============================================
+
+.. meta::
+    :description: Information about the settings you need to configure for your application or site in order to receive traffic from Splunk Synthetic Monitoring.
+
+There are a couple of settings you might need to add to your application or webpage to receive traffic from Splunk Synthetic Monitoring.
+
+
+Allow Splunk Synthetic Monitoring IP addresses
+-------------------------------------------------
+
+Splunk Synthetic Monitoring runs synthetic tests from a set of dedicated IP addresses. To ensure your internal network or web application firewall (WAF) does not block this traffic, place these IP addresses on your browser or site's allow list. 
+
+See :ref:`public-locations` for the list of Splunk Synthetic Monitoring IP addresses, and then refer to your internal network's documentation for instructions on how to add them to your allow list. 
+
+Exclude Splunk Synthetic Monitoring from analytics
+----------------------------------------------------
+If you use a web analytics tool to monitor traffic on your website or application, you might want to exclude Splunk Synthetic Monitoring IP addresses from being counted as traffic. 
+
+To do so, filter Splunk Synthetic Monitoring IP addresses in the settings of your web analytics tool. See :ref:`public-locations` for the list of IP addresses, and then refers to your analytics tool's documentation for instructions on how to filter them. 
+
 
 Choose a test
 ============================================================
@@ -116,12 +140,6 @@ For more examples on Java instrumentation, see :ref:`server-trace-information-ja
 
 Integrate with Splunk RUM so that you can automatically measure Web Vital metrics against your run results. Web vitals capture key metrics that affect user experience and assess the overall performance of your site. For more, see :ref:`rum-synth`.
 
-(Optional) Configure your application
-------------------------------------------------------------------------
-
-
-If you use Splunk Synthetic Monitoring to monitor an application or website with allow/block lists or a web analytics tool, you might want to adjust the settings to accommodate traffic from Splunk Synthetic Monitoring. See :ref:`synth-configure-app` for detailed instructions. 
-
 
 Continue learning
 ==============================

synthetics/syn-troubleshoot/syn-missing-alerts.rst

@@ -0,0 +1,10 @@
+.. _syn-missing-alerts:
+
+*********************************************************
+Troubleshoot missing alerts
+*********************************************************
+
+.. meta::
+    :description: Troubleshoot broken tests   
+
+Troubleshoot missing alerts in Synthetic tests. 

synthetics/syn-troubleshoot/syn-troubleshoot.rst

@@ -0,0 +1,38 @@
+.. _syn-troubleshoot:
+
+****************************************
+Troubleshoot broken tests  
+****************************************
+
+.. meta::
+    :description: Troubleshoot broken tests   
+
+
+
+There are a number of reasons why your tests might fail like issues with test validation or application unresponsiveness. For example, 
+
+* API endpoint was unreachable
+* URL was unreachable
+* UI element wasn't found
+* Default wait time of 10 seconds is too short for step assertions to complete. A test might fail because it takes longer than 10 seconds for a website to load. 
+
+Troubleshoot test validation
+===============================
+
+Follow these guidelines to troubleshoot a broken test. 
+
+#. (Optional) Make a copy of the test so that you can check various solutions before fixing the original test. 
+#. Open the test page and see when the test started to fail. Consider the following questions:
+
+    * When did the check fail? Is there a pattern among other failed runs?
+    * Does the check fail consistently on the same step, or intermittently?
+    * Is this the first time the check has failed on this step? Did you make a recent change to the test?
+    * Was the failure tied to a specific location or across all locations? 
+
+#. Open the run results view of a failed test, find the step that is failing and go to the link. 
+#. Open inspect element. 
+#. Duplicate the step and repeat the steps in your test until you find the broken step. 
+#. Verify that there is one instance only of the selector you want to use in your test. If the selector appears more than once your test might break again in the future. Unique selectors provide optimal test performance. 
+#. Update your tests with your findings. 
+
+

synthetics/test-config/test-config.rst

@@ -1,15 +1,14 @@
 .. _test-config:
 
 ***************************************************
-Manage synthetic tests
+Advanced test configurations
 ***************************************************
 
 .. meta::
     :description: Customize tests run in Splunk Synthetic Monitoring by setting up different devices, variables, locations, test status, and other configurations to best simulate diverse types of traffic to your site or application. 
 
 .. toctree::
 
-   synth-configure-app
    synth-alerts
    built-in-variables
    global-variables
@@ -110,24 +109,13 @@ Choosing informative names for your tests and alerts helps organize content. Her
       :alt: This image shows two Browser tests with the prefix [ButtercupGames].
 
 
-========================================================================================
-Troubleshoot broken tests
-========================================================================================
-Follow these guidelines to troubleshoot a broken test. 
+================================
+Troubleshoot broken tests 
+================================
 
-#. (Optional) Make a copy of the test so that you can check various solutions before fixing the original test. 
-#. Open the test page and see when the test started to fail. Consider the following questions:
+See, :ref:`syn-troubleshoot`.
 
-    * When did the check fail? Is there a pattern among other failed runs?
-    * Does the check fail consistently on the same step, or intermittently?
-    * Is this the first time the check has failed on this step? Did you make a recent change to the test?
-    * Was the failure tied to a specific location or across all locations? 
 
-#. Open the run results view of a failed test, find the step that is failing and go to the link. 
-#. Open inspect element. 
-#. Duplicate the step and repeat the steps in your test until you find the broken step. 
-#. Verify that there is one instance only of the selector you want to use in your test. If the selector appears more than once your test might break again in the future. Unique selectors provide optimal test performance. 
-#. Update your tests with your findings. 
 
 ========================================================================================
 Filter tests

synthetics/uptime-test/uptime-test.rst

@@ -2,7 +2,7 @@
 .. _uptime-test:
 
 **************************************************
-Use an Uptime Test to test port or HTTP uptime
+Uptime Tests for port and HTTP
 **************************************************
 
 .. meta::