Merge pull request #1628 from splunk/repo-sync

Pulling refs/heads/main into main
splunk · Dec 12, 2024 · d04a1e7 · d04a1e7
2 parents c56bf18 + 89c0679
commit d04a1e7
Show file tree

Hide file tree

Showing 302 changed files with 10,033 additions and 36 deletions.
diff --git a/_includes/collector-upgrade.rst b/_includes/collector-upgrade.rst
@@ -14,8 +14,21 @@ Apply the following changes to the Collector configuration files for specific ve
 From 0.96.1 to 0.97.0
 ------------------------------------
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="collector-upgrade-memory-ballast.rst"></div>
+
 .. include:: /_includes/collector-upgrade-memory-ballast.rst
 
+.. raw:: html
+
+   <div class="include-stop" id="collector-upgrade-memory-ballast.rst"></div>
+
+
+
+
 From 0.68.0 to 0.69.0
 ------------------------------------
 

diff --git a/_includes/gdi/java-20-metrics-equivalences.rst b/_includes/gdi/java-20-metrics-equivalences.rst
@@ -57,9 +57,9 @@ The following table shows the metrics produced by default by OpenTelemetry Java
     - ``runtime.jvm.threads.daemon`` |br| ``runtime.jvm.threads.live``
 
 
-:sup:`*` This is a Splunk specific metric and it's not present in the upstream semantic conventions.
+:sup:`*` This is a Splunk-specific metric and it's not present in the upstream semantic conventions.
 
 .. note:: The previous table contains metrics generated by default. Additional metrics might be emitted by supported metrics instrumentation, for example when instrumenting application servers.
 
-For more information on the HTTP semantic convention changes, see :new-page:`HTTP semantic convention stability migration guide <https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/migration-guide.md#summary-of-changes>` on GitHub.
+For more information on the HTTP semantic convention changes, see :new-page:`HTTP semantic convention stability migration guide <https://github.com/open-telemetry/semantic-conventions/blob/main/docs/non-normative/http-migration.md#summary-of-changes>` on GitHub.
 
diff --git a/_includes/gdi/lambda-configuration.rst b/_includes/gdi/lambda-configuration.rst
@@ -1,6 +1,3 @@
-Configure the Splunk OpenTelemetry Lambda layer
-----------------------------------------------------
-
 Follow these steps to add the required configuration for the Splunk OpenTelemetry Lambda layer:
 
 1. In the AWS Lambda console, open the function that you are instrumenting.

diff --git a/admin/authentication/SSO/sso-ADSF.rst b/admin/authentication/SSO/sso-ADSF.rst
@@ -216,4 +216,17 @@ If you want to turn off the email authentication feature, contact :ref:`support`
 
 .. note:: The ADFS portal is the only way that your users can log in to Splunk Observability Cloud.
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="troubleshooting-components.rst"></div>
+
 .. include:: /_includes/troubleshooting-components.rst
+
+.. raw:: html
+
+   <div class="include-stop" id="troubleshooting-components.rst"></div>
+
+
+
diff --git a/admin/authentication/SSO/sso-AzureAD.rst b/admin/authentication/SSO/sso-AzureAD.rst
@@ -46,4 +46,17 @@ If you want to turn off the email authentication feature, contact :ref:`support`
 
 Once you have a custom URL configured, your users can continue to log in using their existing username/password pair, or they can use their Microsoft Entra ID credentials instead. Microsoft Entra ID SSO authentication and Splunk Observability Cloud username/password authentication are independent.
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="troubleshooting-components.rst"></div>
+
 .. include:: /_includes/troubleshooting-components.rst
+
+.. raw:: html
+
+   <div class="include-stop" id="troubleshooting-components.rst"></div>
+
+
+
diff --git a/admin/authentication/SSO/sso-Google.rst b/admin/authentication/SSO/sso-Google.rst
@@ -78,4 +78,17 @@ If you want to turn off the email authentication feature, contact :ref:`support`
 
 Once you have a custom URL configured, your users can continue to log in using their existing username/password pair, or they can use their GCI credentials instead. GCI SSO authentication and Splunk Observability Cloud username/password authentication are independent.
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="troubleshooting-components.rst"></div>
+
 .. include:: /_includes/troubleshooting-components.rst
+
+.. raw:: html
+
+   <div class="include-stop" id="troubleshooting-components.rst"></div>
+
+
+
diff --git a/admin/authentication/SSO/sso-GoogleCloudIDP.rst b/admin/authentication/SSO/sso-GoogleCloudIDP.rst
@@ -29,4 +29,17 @@ If you want to turn off the email authentication feature, contact :ref:`support`
 
 Once you have a custom URL configured, your users can continue to log in using their existing username/password pair, or they can use their GCI credentials instead. GCI SSO authentication and Splunk Observability Cloud username/password authentication are independent.
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="troubleshooting-components.rst"></div>
+
 .. include:: /_includes/troubleshooting-components.rst
+
+.. raw:: html
+
+   <div class="include-stop" id="troubleshooting-components.rst"></div>
+
+
+
diff --git a/admin/authentication/SSO/sso-Okta.rst b/admin/authentication/SSO/sso-Okta.rst
@@ -63,4 +63,17 @@ Once you have a custom URL configured, your users can continue to log in using t
 
 Splunk Observability Cloud generates a password for users you create in Okta SSO. If the Okta login portal is unavailable, Splunk Observability Cloud users can use the reset password link on the Splunk Observability Cloud login page to get native Splunk Observability Cloud credentials.
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="troubleshooting-components.rst"></div>
+
 .. include:: /_includes/troubleshooting-components.rst
+
+.. raw:: html
+
+   <div class="include-stop" id="troubleshooting-components.rst"></div>
+
+
+
diff --git a/admin/authentication/SSO/sso-OneLogin.rst b/admin/authentication/SSO/sso-OneLogin.rst
@@ -61,4 +61,17 @@ Once you have a custom URL configured, your users can continue to log in using t
 
 Splunk Observability Cloud generates a password for users you create in OneLogin SSO. If the OneLogin portal is unavailable, Splunk Observability Cloud users can use the reset password link on the Splunk Observability Cloud login page to get native Splunk Observability Cloud credentials.
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="troubleshooting-components.rst"></div>
+
 .. include:: /_includes/troubleshooting-components.rst
+
+.. raw:: html
+
+   <div class="include-stop" id="troubleshooting-components.rst"></div>
+
+
+
diff --git a/admin/authentication/SSO/sso-PingOne.rst b/admin/authentication/SSO/sso-PingOne.rst
@@ -88,4 +88,17 @@ set up the data mapping from PingOne to Splunk Observability Cloud, follow these
 
 To learn more about mapping Splunk Observability Cloud data fields to PingOne data fields, see the :ref:`saml-user-information` section in the :ref:`sso-generic` topic.
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="troubleshooting-components.rst"></div>
+
 .. include:: /_includes/troubleshooting-components.rst
+
+.. raw:: html
+
+   <div class="include-stop" id="troubleshooting-components.rst"></div>
+
+
+
diff --git a/admin/authentication/SSO/sso.rst b/admin/authentication/SSO/sso.rst
@@ -28,8 +28,21 @@ Splunk Observability Cloud supports the following SSO integrations:
 
 .. _about-realms:
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="realm-note.rst"></div>
+
 .. include:: /_includes/realm-note.rst
 
+.. raw:: html
+
+   <div class="include-stop" id="realm-note.rst"></div>
+
+
+
+
 .. _custom-url:
 
 .. raw:: html

diff --git a/admin/authentication/allow-services.rst b/admin/authentication/allow-services.rst
@@ -153,8 +153,21 @@ Restart the Collector after adding these environment variables to your configura
 URLs to allow in your network
 ================================
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="realm-note.rst"></div>
+
 .. include:: /_includes/realm-note.rst
 
+.. raw:: html
+
+   <div class="include-stop" id="realm-note.rst"></div>
+
+
+
+
 If your organization's networking security policies require you to individually allow services delivered over the internet, ensure that you allow the following service URLs on your network:
 
 .. code:: shell

diff --git a/admin/org-metrics.rst b/admin/org-metrics.rst
@@ -297,4 +297,17 @@ Splunk Observability Cloud provides the following organization metrics:
 Troubleshooting
 ---------------
 
+
+
+.. raw:: html
+
+   <div class="include-start" id="troubleshooting-components.rst"></div>
+
 .. include:: /_includes/troubleshooting-components.rst
+
+.. raw:: html
+
+   <div class="include-stop" id="troubleshooting-components.rst"></div>
+
+
+