Merge pull request #1312 from splunk/repo-sync

Pulling refs/heads/main into main

_includes/gdi/histograms.rst

@@ -1,5 +1,5 @@
 
-To send histogram data to Splunk Observability Cloud, set the ``send_otlp_histogram`` option to ``true``. For example:
+To send histogram data to Splunk Observability Cloud, set the ``send_otlp_histograms`` option to ``true``. For example:
 
 .. code-block:: yaml
    :emphasize-lines: 5
@@ -8,6 +8,6 @@ To send histogram data to Splunk Observability Cloud, set the ``send_otlp_histog
      access_token: "${SPLUNK_ACCESS_TOKEN}"
      api_url: "${SPLUNK_API_URL}"
      ingest_url: "${SPLUNK_INGEST_URL}"
-     send_otlp_histogram: true
+     send_otlp_histograms: true
 
 You can collect histogram data using a variety of receivers, including the :ref:`Prometheus receiver <prometheus-receiver>`.

gdi/opentelemetry/components/signalfx-exporter.rst

@@ -61,7 +61,7 @@ When adding the SignalFx exporter, configure both the metrics and logs pipelines
 Send histogram metrics in OTLP format
 -------------------------------------------
 
-The Splunk Distribution of OpenTelemetry Collector supports OTLP histogram metrics starting from version 0.95 and higher. See :ref:`explicit-bucket-histograms` for more information.
+The Splunk Distribution of OpenTelemetry Collector supports OTLP histogram metrics starting from version 0.98 and higher. See :ref:`explicit-bucket-histograms` for more information.
 
 .. include:: /_includes/gdi/histograms.rst
 

logs/scp.rst

@@ -99,39 +99,19 @@ In Splunk Cloud Platform, follow the instructions in the guided setup for the in
 
 8. Secure a connection to your Splunk Cloud Platform instance in Splunk Observability Cloud. To get help from Splunk Support, :ref:`Submit a support ticket <support-ticket>`. To do it yourself, add your public IPv4 address to your Splunk Cloud Platform allow list by following instructions in :new-page:`Add subnets to IP allow lists <https://docs.splunk.com/Documentation/SplunkCloud/latest/Admin/ConfigureIPAllowList#Add_subnets_to_IP_allow_lists>`. 
 
-   If you are in a GCP environment, add the following additional IP addresses to your Splunk Cloud Platform allow list:
+   If you are in a GCP Splunk Observability Cloud realm, add the following additional IP addresses to your Splunk Cloud Platform allow list:
 
          * 35.247.113.38/32
 
          * 35.247.32.72/32
 
          * 35.247.86.219/32
-
-9. Access your Splunk Cloud Platform management port (for example, stackname.splunkcloud.com:8089) and use your browser's secure connection to download the certificate.
-
-   a. For example, in the Chrome browser, select the lock icon in the address bar, then select :guilabel:`Connection is secure`.
-
-      .. image:: /_images/logs/chrome-secure1A.png
-         :width: 50%
-         :alt: This screenshot shows how to find the lock icon for secure download in Google Chrome.
-
-   b. Next, select :guilabel:`Certificate is valid`.
-
-      .. image:: /_images/logs/chrome-secure2A.png
-         :width: 50%
-         :alt: This screenshot shows how to download a certificate in Google Chrome.
-
-   c. On the :guilabel:`Details` tab, select :guilabel:`Export`.
 
-      .. image:: /_images/logs/chrome-secure3A.png
-         :width: 60%
-         :alt: This screenshot shows how to finish downloading a certificate in Google Chrome.
+9.  Go back to the Log Observer Connect guided setup and select :guilabel:`Next`. Enter your service account username, password, and Splunk platform URL to complete the guided setup.
 
-10.  Go back to the Log Observer Connect guided setup and select :guilabel:`Next`. Enter your service account username, password, and Splunk platform URL, then upload the certificate you downloaded in the previous step to complete the guided setup.
+10.  Remove your IPv4 address from the IP allowlist that you added in step 8. If you are in a GCP environment, do not remove the additional GCP IP addresses that you added in step 8.
 
-11.  Remove your IPv4 address from the IP allowlist that you added in step 8. If you are in a GCP environment, do not remove the additional GCP IP addresses that you added in step 8.
-
-12.  Make sure to give each connection a unique name on the final page of the Log Observer Connect guided setup.
+11.  Make sure to give each connection a unique name on the final page of the Log Observer Connect guided setup.
 
    .. note:: Manage concurrent search limits using your current strategy in Splunk Cloud Platform. All searches initiated by Log Observer Connect users go through the service account you create in Splunk Cloud Platform. For each active Log Observer Connect user, four back-end searches occur when a user performs a search in Log Observer Connect. For example, if there are three users accessing Log Observer Connect at the same time, the service account for Log Observer Connect initiates approximately 12 searches in Splunk Cloud Platform.
 
@@ -160,15 +140,7 @@ To submit a support ticket, follow these steps:
       OrgID: <enter-orgid>
       Realm: <enter-realm>
       Instance Name: <instance-name>
-      Request: Please securely open our Splunk Cloud Platform instance management port (8089) and add the IP addresses of the above realm to our allow list. Also, please provide us with the SSL certificate chain in this ticket so that we can enable Log Observer Connect.
-   
-
-When you receive the SSL certificate from Splunk Support in your support ticket, do the following:
-
-1. Paste the first certificate stanza in the final section of the Log Observer Connect guided setup, :guilabel:`Set up Observability Cloud`.
-
-2. Select :guilabel:`Save and Activate`.
-
+      Request: Please securely open our Splunk Cloud Platform instance management port (8089) and add the IP addresses of the above realm to our allow list so that we can enable Log Observer Connect.
 
 Troubleshooting
 ==============================================================

metrics-and-metadata/histograms-gdi.rst

@@ -9,7 +9,7 @@ Get histogram data into Splunk Observability Cloud
 
 You can collect histogram data using a variety of receivers, including the Prometheus receiver, and send them to Splunk Observability Cloud using the OpenTelemetry Collector. See :ref:`Prometheus receiver <prometheus-receiver>`.
 
-The Splunk Distribution of OpenTelemetry Collector supports explicit-bucket histogram metrics. You can send histogram metric using the OTLP exporter or, starting from version 0.95, through the SignalFx exporter.
+The Splunk Distribution of OpenTelemetry Collector supports explicit-bucket histogram metrics. You can send histogram metric using the OTLP exporter or, starting from version 0.98, through the SignalFx exporter.
 
 .. include:: /_includes/gdi/histograms.rst
 
@@ -57,7 +57,7 @@ Migrate your dashboards, functions, charts, and detectors
 
 To migrate your existing dashboards, functions, charts, and detectors to histograms, follow these steps:
 
-1. Make sure that you're sending histogram data using the Splunk Distribution of OpenTelemetry Collector version 0.95 or higher. Lower versions can't send histogram data in OTLP format using the SignalFx exporter.
+1. Make sure that you're sending histogram data using the Splunk Distribution of OpenTelemetry Collector version 0.98 or higher. Lower versions can't send histogram data in OTLP format using the SignalFx exporter.
 
 2. Start sending histogram metrics through the OTLP exporter or the SignalFx exporter. See :ref:`enable-histograms-export` for more information on how to activate this feature in the Collector.