Merge pull request #2325 from splunk/repo-sync

aurbiztondo-splunk · web-flow · commit 99dad5739af5 · 2024-09-24T08:26:10.000+02:00
Pulling refs/heads/main into main
diff --git a/gdi/opentelemetry/collector-kubernetes/kubernetes-support.rst b/gdi/opentelemetry/collector-kubernetes/kubernetes-support.rst
@@ -33,6 +33,11 @@ In addition, include the following information:
   * Kubernetes version.
   * Managed or on premises: if managed, which cloud provider and distribution?
 
+* ConfigMaps from problematic pods:
+
+  * ``kubectl get cm my-splunk-otel-collector-agent -o yaml > my-splunk-otel-collector-agent-cm.yaml``
+  * ``kubectl get cm my-splunk-otel-collector-k8s-cluster-receiver -o yaml > my-splunk-otel-collector-k8s-cluster-receiver-cm.yaml``
+
 * Logs from problematic pods:
 
   * ``kubectl logs my-splunk-otel-collector-agent-fzn4q otel-collector > my-splunk-otel-collector-agent.log``
diff --git a/gdi/opentelemetry/components/oracledb-receiver.rst b/gdi/opentelemetry/components/oracledb-receiver.rst
@@ -57,7 +57,7 @@ configuration file, as shown in the following example:
    receivers:
      oracledb:
        # Refer to Oracle Go Driver go_ora documentation for full connection string options
-       datasource: "oracle://<user>:<password>@<host>:<port>/<database>"
+       datasource: "oracle://<username>:<password>@<host>:<port>/<database>"
 
 To add more than one instance of Oracle Database, add as many entries of
 the ``oracledb`` receiver as needed. For example:
@@ -67,11 +67,11 @@ the ``oracledb`` receiver as needed. For example:
    receivers:
      oracledb/aninstance:
        # Refer to Oracle Go Driver go_ora documentation for full connection string options
-       datasource: "oracle://<user>:<password>@<host>:<port>/<database>"
+       datasource: "oracle://<username>:<password>@<host>:<port>/<database>"
      
      oracledb/anotherinstance:
        # Refer to Oracle Go Driver go_ora documentation for full connection string options
-       datasource: "oracle://<user>:<password>@<host>:<port>/<database>"
+       datasource: "oracle://<username>:<password>@<host>:<port>/<database>"
 
 To complete the configuration, include the receiver in the ``metrics`` pipeline of the ``service`` section of your
 configuration file. For example:
@@ -84,6 +84,15 @@ configuration file. For example:
          receivers:
            - oracledb
 
+To configure the Oracle Database receiver for high availability use:
+
+.. code:: yaml
+
+   receivers:
+     oracledb:
+       # Refer to Oracle Go Driver go_ora documentation for full connection string options
+       datasource: "oracle://<username>:<password>@<host>:<port>/<service_name>?<server>=<host>:<port>"
+
 Settings
 ======================
 
diff --git a/gdi/opentelemetry/components/splunk-hec-exporter.rst b/gdi/opentelemetry/components/splunk-hec-exporter.rst
@@ -95,8 +95,8 @@ The Splunk HEC exporter requires a Splunk HEC token and endpoint. Obtaining a HE
      - See :new-page:`Send data to HTTP Event Collector on Splunk Enterprise <https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector#Send_data_to_HTTP_Event_Collector_on_Splunk_Enterprise>`
      - See :new-page:`Create an Event Collector token on Splunk Enterprise <https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector#Create_an_Event_Collector_token_on_Splunk_Enterprise>`
    * - Splunk Observability Cloud
-     - See :ref:`admin-org-tokens`.
      - ``https://ingest.<realm>.signalfx.com/v1/log``, where ``<realm>`` is the Splunk Observability Cloud realm, for example ``us0``.
+     - See :ref:`admin-org-tokens`.
 
 To find your Splunk realm, see :ref:`Note about realms <about-realms>`.
 
diff --git a/metrics-and-metadata/search.rst b/metrics-and-metadata/search.rst
@@ -63,6 +63,6 @@ You can either search a specific term, or define what type of object you're look
        :width: 100%
        :alt: Search results for "“checkoutservice".
 
-#. (Optional) You can narrow the search to specific types of results using the following supported prefixes. Use prefeixes to focus search results to a single category. For details, see :ref:`prefix`.
+#. (Optional) You can narrow the search to specific types of results using the following supported prefixes. Use prefixes to focus search results to a single category. For details, see :ref:`prefix`.
 #. (Optional) Select a "more results" link to see more matching results in the search category. 
 #. Select one of the search results to be taken to that object.
diff --git a/sp-oncall/notifications/notification-types.rst b/sp-oncall/notifications/notification-types.rst
@@ -72,6 +72,13 @@ incident number, entity_display_name, and response code if two-way SMS is suppor
 
 You may stop and start our SMS notification subscription by replying to the message with STOP or START. Although, it is best to manage your notifications from the personal profile page in Splunk On-Call.
 
+.. raw:: html
+
+  <embed>
+    <h2>WhatsApp</h2>
+  </embed>
+
+You can use WhatsApp notifications in your personal paging policy. To enable WhatsApp, download and configure the WhatsApp application from the Apple App Store or Google Play Store. Next, access your user profile in Splunk On-Call and enter and verify your mobile number. After verification, an :guilabel:`Enable WhatsApp` button will appear next to the number and you'll be able to use WhatsApp in your Paging Policy.
 
 .. raw:: html
 
diff --git a/sp-oncall/spoc-integrations/slack-integration-guide.rst b/sp-oncall/spoc-integrations/slack-integration-guide.rst
@@ -22,6 +22,7 @@ You must be a Slack administrator to configure this integration. If you prefer n
 
 .. caution:: Deactivate the old Slack (webhook) integration prior to activating the Slack integration.
 
+In Splunk On-Call, you must have either Global or Alert Admin permissions to set up and adjust this integration.
 
 Slack configuration
 ==========================
diff --git a/synthetics/test-config/private-locations.rst b/synthetics/test-config/private-locations.rst
@@ -171,7 +171,28 @@ NO_PROXY is configured to bypass the proxy for local addresses and specific doma
 
 Ensure that these variables are correctly configured to comply with your network policies. This setup allows the synthetic tests to communicate securely and efficiently in a controlled network environment.
 
-
+When using runner, it's important to correctly configure the proxy settings to avoid issues with browser-based tests. The following steps should be followed when setting up their environment:
+
+1. :strong:`Ensure Proper NO_PROXY Setup`:
+   
+   - When configuring ``NO_PROXY`` always include the following addresses:
+   
+     - ``127.0.0.1`` (for localhost communication)
+     - ``localhost`` (for resolving local tests)
+   
+   These addresses ensure that internal services and tests run correctly without routing through a proxy, preventing potential failures.
+
+2. :strong:`Merging HTTP_PROXY and http_proxy`:
+   
+   - The system automatically handles both ``HTTP_PROXY`` and ``http_proxy`` environment variables. If you define one of these, ensure the other is also set, or they will be automatically merged at start-up.
+
+3. :strong:`Dockerfile defaults`:
+   
+   - By default, the runner will set the ``NO_PROXY`` variable in the Dockerfile to include ``127.0.0.1``. If you override ``NO_PROXY``, you must ensure that ``127.0.0.1`` and ``localhost`` are still present, or browser tests may fail.
+
+4. :strong:`Startup Check`:
+   
+   - The runner includes a startup check to validate that ``NO_PROXY`` contains ``127.0.0.1`` and ``localhost``. If these are missing, you might encounter unexpected behavior in test execution.
 
 
 
