Merge pull request #2453 from splunk/repo-sync

Pulling refs/heads/main into main

Author: aurbiztondo-splunk

admin/references/data-retention.rst

@@ -60,6 +60,9 @@ The following table shows the retention time period for each data type in RUM.
    * - :ref:`Monitoring MetricSets <monitoring-metricsets>`
      - 
        * 13 months 
+   * - :ref:`Session Replay <rum-session-replay>` 
+     - 
+       * 8 days
 
 .. _apm-data-retention:
 

gdi/get-data-in/application/java/instrumentation/instrument-java-application.rst

@@ -260,12 +260,16 @@ If you need to send data directly to Splunk Observability Cloud, set the followi
    .. code-tab:: bash Linux
 
       export SPLUNK_ACCESS_TOKEN=<access_token>
-      export SPLUNK_REALM=<realm>
+      export OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf
+      export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://ingest.<realm>.signalfx.com/v2/trace/otlp
+      export OTEL_LOGS_EXPORTER=none
 
    .. code-tab:: shell Windows PowerShell
 
       $env:SPLUNK_ACCESS_TOKEN=<access_token>
-      $env:SPLUNK_REALM=<realm>
+      $env:OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf
+      $env:OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://ingest.<realm>.signalfx.com/v2/trace/otlp
+      $env:OTEL_LOGS_EXPORTER=none
 
 To obtain an access token, see :ref:`admin-api-access-tokens`.
 

splunkplatform/unified-id/unified-identity.rst

@@ -164,7 +164,7 @@ If you already have a Splunk Cloud Platform account and a Splunk Observability C
               "status": "SUCCESS"
 
 
-Users will receive an email telling them to authenticate to Splunk Observability Cloud using the new authentication method through Splunk Cloud Platform SSO. Note that users can continue to use their previous login method. If you want to force all users to authenticate through Splunk Cloud Platform SSO, reach out to Splunk Customer Support to deactivate local login. To deactivate login through a third party identity provider, go to :strong:`Data Managemen > Available integrations` in Splunk Observability Cloud, select the appropriate integration (for example, Okta), and select :strong:`Deactivate`. 
+Users will receive an email telling them to authenticate to Splunk Observability Cloud using the new authentication method through Splunk Cloud Platform SSO. Note that users can continue to use their previous login method. If you want to force all users to authenticate through Splunk Cloud Platform SSO, reach out to Splunk Customer Support to deactivate local login. To deactivate login through a third party identity provider, go to :strong:`Data Management > Available integrations` in Splunk Observability Cloud, select the appropriate integration (for example, Okta), and select :strong:`Deactivate`. 
 
 
 .. _unified-id-user-provisioning: