Pulling refs/heads/main into main

_includes/gdi/available-gcp.rst

@@ -28,7 +28,7 @@ You can collect data from the following GCP services out-of-the-box:
   * - cloudfunctions
     - Cloud Functions
     - :strong:`X`
-    - 
+    - :strong:`X`
 
   * - cloudiot
     - Cloud Internet of Things Core
@@ -38,7 +38,7 @@ You can collect data from the following GCP services out-of-the-box:
   * - cloudsql
     - Cloud SQL
     - :strong:`X`
-    - 
+    - :strong:`X`
 
   * - cloudtasks
     - Cloud Tasks
@@ -128,7 +128,7 @@ You can collect data from the following GCP services out-of-the-box:
   * - pubsub
     - Cloud Pub/Sub
     - :strong:`X`
-    - 
+    - :strong:`X`
 
   * - redis
     - Memorystore for Redis
@@ -143,7 +143,7 @@ You can collect data from the following GCP services out-of-the-box:
   * - run
     - Cloud Run
     - :strong:`X`
-    - 
+    - :strong:`X`
 
   * - serviceruntime
     - Google Cloud Endpoints APIs

gdi/get-data-in/connect/gcp/gcp-connect.rst

@@ -70,7 +70,7 @@ Alternatively you can create a more restrictive role using the permissions in th
       - Yes
 
    *  - ``serviceusage.services.use``
-      - Yes, if you want to activate the use of a quota from the project where metrics are stored
+      - Yes, if you either want to activate the use of a quota from the project where metrics are stored or sync cloud sql metadata
       - No, but included in ``roles/serviceusage.serviceUsageConsumer``
 
    *  - ``spanner.instances.list``
@@ -81,6 +81,39 @@ Alternatively you can create a more restrictive role using the permissions in th
       - Yes, if the Spanner service is activated
       - Yes
 
+   *  - ``cloudsql.databases.list``
+      - Yes, if the cloud sql service is activated
+      - Yes
+
+   *  - ``cloudsql.instances.list``
+      - Yes, if the cloud sql service is activated
+      - Yes
+
+   *  - ``pubsub.topics.list``
+      - Yes, if the pub/sub service is activated
+      - Yes
+
+   *  - ``pubsub.subscriptions.list``
+      - Yes, if the pub/sub service is activated
+      - Yes
+
+   *  - ``run.jobs.list``
+      - Yes, if the cloud run service is activated
+      - Yes
+
+   *  - ``run.revisions.list``
+      - Yes, if the cloud run service is activated
+      - Yes
+
+   *  - ``cloudasset.assets.searchAllResources``
+      - Yes, if the cloud run service is activated
+      - Yes
+
+   *  - ``cloudfunctions.functions.list``
+      - Yes, if the cloud functions service is activated
+      - Yes
+
+
 .. _gcp-two:
 
 2. Configure GCP

get-started/get-started-guide/get-started-guide.rst

@@ -75,11 +75,11 @@ The journey for getting started with Splunk Observability Cloud has 3 phases: on
      - * :ref:`advanced-config-custom-URL`
        * :ref:`advanced-config-parent-child`
        * :ref:`advanced-config-logs`
-       * :ref:`advanced-config-3rd-party`
 
        See :ref:`Phase 1 optional and advanced configurations <phase1-advanced-config>`.
 
-     - * :ref:`phase3-network-exp`
+     - * :ref:`advanced-config-3rd-party`
+       * :ref:`phase3-network-exp`
        * :ref:`phase2-profiling`
        * :ref:`phase2-related-content`
 

get-started/get-started-guide/initial-rollout.rst

@@ -96,6 +96,15 @@ Optional and advanced configurations
 
 Consider these optional and advanced configurations to customize your setup as they apply to your organization. 
 
+.. _advanced-config-3rd-party:
+
+Collect data from third-party metrics providers
+--------------------------------------------------------------
+
+When using the Splunk Distribution of OpenTelemetry Collector, you can use receivers to collect metrics data from third-party providers. For example, you can use the Prometheus receiver to scrape metrics data from any application that exposes a Prometheus endpoint. See :ref:`prometheus-receiver`.
+
+See :ref:`monitor-data-sources` for a list of receivers.
+
 .. _phase3-network-exp:
 
 Set up Network Explorer to monitor network environment

get-started/get-started-guide/onboarding-readiness.rst

@@ -132,15 +132,6 @@ If your organization has an entitlement for Splunk Log Observer Connect, Splunk
 
 See :ref:`logs-set-up-logconnect` or :ref:`logs-scp`. 
 
-.. _advanced-config-3rd-party:
-
-Collect data from third-party metrics providers
---------------------------------------------------------------
-
-When using the Splunk Distribution of OpenTelemetry Collector, you can use receivers to collect metrics data from third-party providers. For example, you can use the Prometheus receiver to scrape metrics data from any application that exposes a Prometheus endpoint. See :ref:`prometheus-receiver`.
-
-See :ref:`monitor-data-sources` for a list of receivers.
-
 Education resources
 =====================
 

index.rst

@@ -770,12 +770,6 @@ To keep up to date with changes in the products, see the Splunk Observability Cl
 
    Troubleshoot tests TOGGLE <synthetics/syn-troubleshoot/syn-troubleshoot>
 
-
-.. toctree::
-   :maxdepth:   3
-
-   Troubleshoot tests  <synthetics/syn-troubleshoot/syn-missing-alerts>
-
 .. toctree::
    :caption: Splunk On-Call
    :maxdepth:   3

sp-oncall/spoc-integrations/servicenow-integration.rst

@@ -26,7 +26,7 @@ You can do the following with the integration:
 Requirements
 =====================
 
-* ServiceNow versions supported: Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah
+* ServiceNow versions supported: Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington DC, Xanadu
 *  ServiceNow account: Requires ServiceNow Administrative Privileges to create the application registry and an Active, Web Service Access only user with the ITIL role.
 * Splunk On-Call version required: Enterprise level of service
 
@@ -125,7 +125,7 @@ Preconfigured fields that are immediately available are:
 * assigned_to
 * resolved_by
 
-You can set all the preconfigured fields using the rules engine using the followig syntax: ``ServiceNowField_victorops\_<field_name>``. 
+You can set all the preconfigured fields using the rules engine using the following syntax: ``ServiceNowField_victorops\_<field_name>`` or ``ServiceNowField_u_victorops\_<field_name>``.  The particular syntax will depend on the specific ServiceNow environment version and may require testing.
 
 The following fields are automatically handled by the integration mapping:
 
@@ -161,7 +161,7 @@ Only some fields are preconfigured with the VictorOps app, so mapping additional
    #. Last, make sure the 2 fields are mapped,in the :guilabel:`Field Map` field. 
    #. Select :guilabel:`Save`.
 
-Now you can use the Splunk On-Call alert rules engine to supply the field values with the same syntax as before: set ``ServiceNowField_<field_name>`` to new value ``<value>``.
+Now you can use the Splunk On-Call alert rules engine to supply the field values with the same syntax as before: set ``ServiceNowField_<field_name>`` OR ``ServiceNowField_u_victorops\_<field_name>`` (depending on ServiceNow version) to new value ``<value>``.
 
 In the following example image, the field value on the Splunk On-Call import table in ServiceNow is ``victorops_custom_field``.