Merge pull request #1699 from splunk/repo-sync

aurbiztondo-splunk · web-flow · commit afba65b1f1f3 · 2025-03-24T15:42:48.000+01:00
Pulling refs/heads/main into main
diff --git a/.github/workflows/heretto-reminder.yml b/.github/workflows/heretto-reminder.yml
@@ -0,0 +1,39 @@
+name: Heretto Update Reminder
+
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+jobs:
+  reminder:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+      actions: read
+      issues: write
+      checks: write
+      pull-requests: write
+
+
+    steps:
+      - name: Add PR Comment
+        uses: actions/github-script@v6
+        with:
+          github-token: ${{ secrets.MY_TOKEN }}
+          script: |
+            const { owner, repo, number } = context.issue;
+            const pr = await github.rest.pulls.get({
+              owner,
+              repo,
+              pull_number: number,
+            });
+
+            const author = pr.data.user.login;
+
+            await github.rest.issues.createComment({
+              owner,
+              repo,
+              issue_number: number,
+              body: `@${author}, please make sure that you update the files in Heretto and post the Heretto share link in this PR.`
+            })
diff --git a/_templates/404.html b/_templates/404.html
@@ -204,7 +204,7 @@ <h2 style="font-size:21px;font-family: 'Open Sans'; font-weight: bold;">Was this
       <a href="https://www.splunk.com/en_us/legal/privacy/privacy-policy.html" target="_blank">Privacy</a> | 
       <a href="https://www.splunk.com/en_us/legal/terms/terms-of-use.html" target="_blank">Terms</a> | 
       <a href="https://www.splunk.com/en_us/legal/export-controls.html" target="_blank">Export Control</a> | 
-      <span style="color:black">&copy; 2005 - 2023 Splunk LLC All rights reserved.</span>
+      <span style="color:black">&copy; 2005 - 2025 Splunk LLC All rights reserved.</span>
       <div class="newfootertxt" style="color:black">Splunk, Splunk>, Turn Data Into Doing, and Data-to-Everything are trademarks or registered trademarks of Splunk LLC in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.</div>
       </div>
       <div style="width: 28%;">
diff --git a/_templates/layout.html b/_templates/layout.html
@@ -208,7 +208,7 @@ <h2 style="font-size:21px;font-family: 'Open Sans'; font-weight: bold;">Was this
       <a href="https://www.splunk.com/en_us/legal/privacy/privacy-policy.html" target="_blank">Privacy</a> | 
       <a href="https://www.splunk.com/en_us/legal/terms/terms-of-use.html" target="_blank">Terms</a> | 
       <a href="https://www.splunk.com/en_us/legal/export-controls.html" target="_blank">Export Control</a> | 
-      <span style="color:black">&copy; 2005 - 2023 Splunk LLC All rights reserved.</span>
+      <span style="color:black">&copy; 2005 - 2025 Splunk LLC All rights reserved.</span>
       <div class="newfootertxt" style="color:black">Splunk, Splunk>, Turn Data Into Doing, and Data-to-Everything are trademarks or registered trademarks of Splunk LLC in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.</div>
       </div>
       <div style="width: 28%;">
diff --git a/_templates/search.html b/_templates/search.html
@@ -268,7 +268,7 @@ <h2 style="font-size:21px;font-family: 'Open Sans'; font-weight: bold;">Was this
         <a href="https://www.splunk.com/en_us/legal/privacy/privacy-policy.html" target="_blank">Privacy</a> |
         <a href="https://www.splunk.com/en_us/legal/terms/terms-of-use.html" target="_blank">Terms</a> |
         <a href="https://www.splunk.com/en_us/legal/export-controls.html" target="_blank">Export Control</a> |
-        <span style="color:black">&copy; 2005 - 2023 Splunk LLC All rights reserved.</span>
+        <span style="color:black">&copy; 2005 - 2025 Splunk LLC All rights reserved.</span>
         <div class="newfootertxt" style="color:black">Splunk, Splunk>, Turn Data Into Doing, and Data-to-Everything are trademarks or registered trademarks of Splunk LLC in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.</div>
     </div>
     <div style="width: 28%;">
diff --git a/gdi/get-data-in/application/otel-dotnet/instrumentation/manual-dotnet-instrumentation.rst b/gdi/get-data-in/application/otel-dotnet/instrumentation/manual-dotnet-instrumentation.rst
@@ -90,4 +90,4 @@ To create custom metrics, follow these steps:
 
       OTEL_DOTNET_AUTO_METRICS_ADDITIONAL_SOURCES=My.Application
 
-See the :new-page:`OpenTelemetry official documentation <https://opentelemetry.io/docs/languages/net/instrumentation/#metrics` for additional information and examples.
+See the :new-page:`OpenTelemetry official documentation <https://opentelemetry.io/docs/languages/net/instrumentation/#metrics>` for additional information and examples.
diff --git a/gdi/get-data-in/connect/aws/aws-connect-polling.rst b/gdi/get-data-in/connect/aws/aws-connect-polling.rst
@@ -54,7 +54,7 @@ In this step you need to choose the following connection options:
 
   * Metadata.
   * Cost and usage metrics.
-  * CloudWatch metrics. 
+  * CloudWatch metrics.
 
 In the CloudWatch Metrics option, select :guilabel:`Polling` as the ingestion method, and set up the polling rate at which you want Splunk Observability Cloud to poll CloudWatch for metric data.
 
diff --git a/gdi/get-data-in/connect/aws/get-awstoc.rst b/gdi/get-data-in/connect/aws/get-awstoc.rst
@@ -8,27 +8,27 @@ Connect AWS to Splunk Observability Cloud
   :description: Connection planning information and links to the different ways to connect AWS to Splunk Observability Cloud.
 
 .. toctree::
-  :hidden:
-  :maxdepth: 5
-
-  AWS authentication, permissions and regions <aws-prereqs>
-  Supported Amazon services <https://docs.splunk.com/observability/en/gdi/integrations/cloud-aws.html#cloud-aws>
-  Compare connection options <aws-compare-connect>
-  Connect via polling <aws-connect-polling>
-  Connect with Splunk-managed Metrics Streams <aws-connect-ms>
-  Connect with AWS-managed Metric Streams <aws-console-ms>  
-  Connect to AWS using the Splunk API <aws-apiconfig>  
-  Connect to AWS with Terraform <aws-terraformconfig>
-  CloudFormation and Terraform templates <aws-cloudformation>
-  Send AWS logs to Splunk Platform <aws-logs>
-  Next steps <aws-post-install>
-  Troubleshoot your AWS integration <aws-troubleshooting>
-  Troubleshoot AWS CloudWatch polling <aws-ts-polling>
-  Troubleshoot Splunk-managed Metric Streams <aws-ts-metric-streams>
-  Troubleshoot AWS-managed Metric Streams <aws-ts-ms-aws>
-  aws-recommended-stats.rst
-  GetMetricStatistics API deprecation notice <aws-api-notice>
-  aws-tutorial/about-aws-tutorial.rst
+   :hidden:
+   :maxdepth: 5
+
+   AWS authentication, permissions and regions <aws-prereqs>
+   Supported Amazon services <https://docs.splunk.com/observability/en/gdi/integrations/cloud-aws.html#cloud-aws>
+   Compare connection options <aws-compare-connect>
+   Connect via polling <aws-connect-polling>
+   Connect with Splunk-managed Metrics Streams <aws-connect-ms>
+   Connect with AWS-managed Metric Streams <aws-console-ms>  
+   Connect to AWS using the Splunk API <aws-apiconfig>  
+   Connect to AWS with Terraform <aws-terraformconfig>
+   CloudFormation and Terraform templates <aws-cloudformation>
+   Send AWS logs to Splunk Platform <aws-logs>
+   Next steps <aws-post-install>
+   Troubleshoot your AWS integration <aws-troubleshooting>
+   Troubleshoot AWS CloudWatch polling <aws-ts-polling>
+   Troubleshoot Splunk-managed Metric Streams <aws-ts-metric-streams>
+   Troubleshoot AWS-managed Metric Streams <aws-ts-ms-aws>
+   aws-recommended-stats.rst
+   GetMetricStatistics API deprecation notice <aws-api-notice>
+   aws-tutorial/about-aws-tutorial.rst
 
 Splunk Observability Cloud offers you several data ingestion and connection methods to monitor your Amazon Web Services (AWS) data. 
 
diff --git a/gdi/get-data-in/rum/browser/configure-rum-browser-instrumentation.rst b/gdi/get-data-in/rum/browser/configure-rum-browser-instrumentation.rst
@@ -200,7 +200,7 @@ The following example shows how to restrict sampling to logged in users:
             rumAccessToken: '<your_rum_token>',
             applicationName: '<application-name>',
             tracer: {
-               sampler: shouldTrace ? new AlwaysOnSampler() : new SplunkRum.AlwaysOffSampler(),
+               sampler: shouldTrace ? new SplunkRum.AlwaysOnSampler() : new SplunkRum.AlwaysOffSampler(),
             },
          });
       </script>
diff --git a/index.rst b/index.rst
@@ -861,3 +861,4 @@ To keep up to date with changes in the products, see the Splunk Observability Cl
    :maxdepth:   3
 
    Contribute to our documentation <get-started/contribute>
+
diff --git a/infrastructure/metrics-pipeline/use-case-archive.rst b/infrastructure/metrics-pipeline/use-case-archive.rst
@@ -41,7 +41,7 @@ Actions
 
 Kai decides to use Archived Metrics to control how Splunk Observability Cloud stores their team's data.
 
-#. In Splunk Observability Cloud, Kai goes to :guilabel:` Settings > Metrics Management`. In the :guilabel:`Pipeline Management` tab Kai searches for the metric ``service.latency`` and configures the ingestion route to Archived Metrics. Kai can now see all the MTS as Archived MTS.
+#. In Splunk Observability Cloud, Kai goes to :guilabel:`Settings` then :guilabel:`Metrics Management`. In the :guilabel:`Pipeline Management` tab Kai searches for the metric ``service.latency`` and configures the ingestion route to Archived Metrics. Kai can now see all the MTS as Archived MTS.
 #. Kai creates a route exception rule and specifies a filter where ``data_center_region = Europe``. This gives them the estimate of 2,497 Real-Time MTS. Kai also restores the previous hour data to make sure they don't have gaps.
 #. Now, Kai views the list of charts and detectors that use ``service.latency``. To learn more about viewing or downloading the list, see :ref:`metrics-usage-report`.
 #. Kai already had a filter set up on the charts and detectors for ``data_center_region = Europe``. Kai verifies the data is visible in one of the charts.
diff --git a/infrastructure/monitor/k8s-nav.rst b/infrastructure/monitor/k8s-nav.rst
@@ -64,8 +64,8 @@ The following table describes the Kubernetes navigators:
 
 .. _k8s-nav-hierarchy-map:
 
-Hierarchy map
-======================
+Investigate instances with the hierarchy map
+===============================================
 
 .. note:: The hierarchy map is only available on the Kubernetes nodes, pods, and containers navigators.
 
@@ -84,8 +84,10 @@ Nodes, pods, and containers are colored by health and status, as reported by Kub
     * Pods are colored by phase: ``Running``, ``Pending``, ``Succeeded``, ``Failed``, and ``Unknown``
     * Containers are colored by status: ``Ready``, ``Not Ready``, and ``Unknown``
 
-Investigate instances in the hierarchy map
----------------------------------------------
+Hierarchy map features
+------------------------
+
+To investigate instances with the hierarchy map, use the following features:
 
 * Breadcrumb navigation: Switch to different instances and jump across entity levels using the breadcrumb navigation bar.
 * Hover: Get more information about an instance, including its status or phase, by hovering over that instance.
@@ -94,15 +96,15 @@ Investigate instances in the hierarchy map
 
 .. _k8s-nav-left-nav:
 
-Left navigation panel
-============================
+Refine your view with the left navigation panel
+==================================================
 
-Use the left navigation panel in the table or heat map view to quickly switch between Kubernetes entity types, search for filters, and access predefined filters.
+Use the left navigation panel in the table or heat map view to quickly switch between Kubernetes entity types, search for filters, use predefined filters, and view or use recently used filters.
 
-To use the left navigation panel:
+To refine your view with the left navigation panel, use the following features:
 
 * :guilabel:`Select entity type`: Use this drop-down menu to switch between Kubernetes entity types.
-* :guilabel:`Refine by`: Use this panel to search for filters or access a list of predefined filters. The list of predefined filters is searchable and organized by :guilabel:`Relationship` and :guilabel:`Attribute`.
+* :guilabel:`Refine by`: Use this panel to search for filters, use predefined filters, or view and use recently used filters. The list of predefined filters is searchable and organized by :guilabel:`Relationship` and :guilabel:`Attribute`.
 
 .. _k8s-nav-analyzer-overview:
 
diff --git a/sp-oncall/admin/get-started/team-dashboard.rst b/sp-oncall/admin/get-started/team-dashboard.rst
@@ -1,23 +1,23 @@
 .. _team-dashboard:
 
 ************************************************************************
-Splunk On-Call 
+Splunk On-Call team dashboard
 ************************************************************************
 
 .. meta::
    :description: Splunk On-Call system requirements, including browsers, mobile support, and incident requirements.
 
 
 
-The Splunk On-Call  provides a comprehensive overview of incidents. This view automatically defaults to the teams that you are a member of and allows teams to dive into the details and understand the status of alerts or incidents. 
+The Splunk On-Call provides a comprehensive overview of incidents. This view automatically defaults to the teams that you are a member of and allows teams to dive into the details and understand the status of alerts or incidents. 
 
-All incidents derived from integrated monitoring tools in the incident table include  their respective logos to help you rapidly identify the source of an alert. Manually created incidents, along with incidents originating from the Email Endpoint or the REST API integrations, will remain logo free.
+All incidents derived from integrated monitoring tools in the incident table include their respective logos to help you rapidly identify the source of an alert. Manually created incidents, along with incidents originating from the Email Endpoint or the REST API integrations, will remain logo free.
 
 Information Alerts can still be found on the Timeline Page.
 
 .. image:: /_images/spoc/team-dashboard.png
     :width: 100%
-    :alt: An image of the . On-Call individuals listed on the left; Team incidents are shown in the main pane.
+    :alt: An image of the team dashboard On-Call individuals listed on the left; Team incidents are shown in the main pane.
 
 
 Filters
@@ -44,12 +44,12 @@ Quickly identify responsible parties during a firefight by easily seeing which p
 Manual Incident Creation
 ----------------------------
 
-You can create a manual incident from the  by selecting :guilabel:`Create Incident` in the top right corner.  For instructions, see :ref:`manual-incident`.
+You can create a manual incident from the team dashboard by selecting :guilabel:`Create Incident` in the top right corner. For instructions, see :ref:`manual-incident`.
 
 Incident War Rooms
 ----------------------------
 
-Access Incident Details directly from the  by selecting the incident number link. This will expand the incident and its event history in the :ref:`Incident War Room <war-room>`. 
+Access Incident Details directly from the team dashboard by selecting the incident number link. This will expand the incident and its event history in the :ref:`Incident War Room <war-room>`. 
 
 People Table
 ==================
diff --git a/sp-oncall/admin/sso/sp-sso-adfs.rst b/sp-oncall/admin/sso/sp-sso-adfs.rst
@@ -7,45 +7,28 @@ Configure Active Directory Federation Services Single Sign-On for Splunk On-Call
 .. meta::
    :description: Enable Splunk On-Call SSO for Active Directory Federation Services (ADFS) your organization. 
 
-
-
-
 Requirements
 ==================
 
 This integration is compatible with the following versions of Splunk On-Call:
 
 - Full-Stack
 
-To enable single sign-on (SSO) for your organization, you will need to provide an updated metadata file and your IDP. If you are
-interested in setting up SSO, please contact :ref:`Splunk On-Call Support <spoc-support>`.
-
-
+To enable single sign-on (SSO) for your organization, you will need to provide an updated metadata file and your IDP. If you are interested in setting up SSO, please contact :ref:`Splunk On-Call Support <spoc-support>`.
 
-Configure Single Sign On (SSO) between your Identity Provider (IDP) and  Splunk On-Call. Our standard SSO setup uses SAML 2.0 protocol. As long as your IDP can use SAML 2.0 protocol, it can integrate with Splunk On-Call. The exact steps differ depending on which IDP you use, but the process typically involves exporting a .XML metadata file and sending it to our Support team. Once you have sent the .xml file, a Splunk On-Call support specialist will
+Our standard SSO setup uses SAML 2.0 protocol. As long as your IDP can use SAML 2.0 protocol, it can integrate with Splunk On-Call. The exact steps differ depending on which IDP you use, but the process typically involves exporting a .XML metadata file and sending it to our Support team. Once you have sent the .xml file, a Splunk On-Call support specialist will
 complete the setup on the back-end and respond with confirmation.
 
 If your IDP does not have SAML capability, please contact Splunk On-Call Support to explore what alternative options may be available. For details on how to contact Splunk On-Call Support, see :ref:`spoc-support`.
 
-
-Administrator Setup
-==========================
-
-Instructions to complete the SSO configuration with Splunk On-Call and your IDP are provided for:
-
-- :ref:`sso-okta-spoc`
-- :ref:`sso-google-spoc`
-- :ref:`sso-onelogin-spoc`
-- :ref:`sso-adfs-ac-spoc`
-
-
 .. _sso-adfs-ac-spoc:
 
+Configure SSO for Active Directory Federation Services (ADFS)
+==============================================================
 
-Active Directory Federation Services (ADFS)
-===========================================================
+To configure SSO for Splunk On-Call using ADFS complete the following steps.
 
-Once you have sent over your Metadata file, and the Splunk On-Call Support team has completed the configuration, you will receive an updated metadata file to complete the configuration on your side.
+#. Once you have sent over your Metadata file and the Splunk On-Call Support team has completed the configuration, you will receive an updated metadata file to complete the configuration on your side.
 
 #. In the ADFS Management console, navigate to :guilabel:`Trust Relationships`, then :guilabel:`Relying Party Trusts` and select :guilabel:`Add Relying Party Trust` in the :menuselection:`Actions` pane.
 
diff --git a/sp-oncall/admin/sso/sp-sso-google.rst b/sp-oncall/admin/sso/sp-sso-google.rst
@@ -7,7 +7,7 @@ Configure Single Sign-On for Splunk On-Call using Google Apps
 .. meta::
    :description: Enable Splunk On-Call SSO for your organization. 
 
-To configure SSO for Splunk On-Call using Google Apps:
+To configure SSO for Splunk On-Call using Google Apps complete the following steps.
 
 #. Access the Admin portal for Google Apps and navigate to :guilabel:`Apps` then :guilabel:`SAML Apps`.
 
diff --git a/sp-oncall/admin/sso/sp-sso-okta.rst b/sp-oncall/admin/sso/sp-sso-okta.rst
@@ -7,9 +7,6 @@ Configure Single Sign-On for Okta and Splunk On-Call
 .. meta::
    :description: Enable Splunk On-Call SSO for your organization. 
 
-
-
-
 Requirements
 ==================
 
@@ -20,20 +17,10 @@ This integration is compatible with the following versions of Splunk On-Call:
 To enable single sign-on (SSO) for your organization, you will need to provide an updated metadata file and your IDP. If you are
 interested in setting up SSO, please contact :ref:`Splunk On-Call Support <spoc-support>`.
 
-
-Administrator Setup
+Configure SSO for Okta
 ==========================
 
-Instructions to complete the SSO configuration with Splunk On-Call and your IDP are provided for:
-
-- :ref:`sso-okta-spoc-setup`
-- :ref:`sso-google-spoc`
-- 
-
-.. _sso-okta-spoc-setup:
-
-Okta
-==========
+To configure SSO for Okta complete the following steps.
 
 #. From the Okta user homepage, select :guilabel:`Admin` to access the Okta Admin dashboard.
 
diff --git a/sp-oncall/alerts/team-escalation-policy.rst b/sp-oncall/alerts/team-escalation-policy.rst
@@ -11,7 +11,7 @@ Escalation policies determine set who is actually on-call for a given team and a
 
 Some things to note:
 
-- Only Team and Global Admins are able to make changes to Escalation Policies
+- Only Team and Global Admins are able to make changes to Escalation Policies.
 - Only users specified in the first step of an Escalation Policy will receive Timeline and Push notifications that they are on-call and will log hours in the on-call report as being on-call. If you would like users in subsequent steps of an escalation policy to receive these notifications and log these hours, see :ref:`multi-escalation-policies`.
 - When an Escalation Policy is executed and a user is being notified, the user's personal paging policy determines how they will be contacted. See :ref:`custom-paging-policy`.
 
diff --git a/sp-oncall/incidents/incident-pane.rst b/sp-oncall/incidents/incident-pane.rst
@@ -5,7 +5,7 @@ Incident Pane
 ************************************************************************
 
 .. meta::
-   :description: About the Incident pane in Splunk On-Call which displays incoming alerts.
+   :description: About the incident pane in Splunk On-Call which displays incoming alerts.
 
 .. toctree::
     :hidden:
diff --git a/sp-oncall/notifications/call-notification-numbers.rst b/sp-oncall/notifications/call-notification-numbers.rst
diff --git a/sp-oncall/reports/post-incident-review.rst b/sp-oncall/reports/post-incident-review.rst
diff --git a/splunkplatform/unified-id/unified-identity.rst b/splunkplatform/unified-id/unified-identity.rst
diff --git a/synthetics/api-test/api-test.rst b/synthetics/api-test/api-test.rst

Original file line number	Diff line number	Diff line change
`@@ -90,4 +90,4 @@ To create custom metrics, follow these steps:`
`90`	`90`
`91`	`91`	`OTEL_DOTNET_AUTO_METRICS_ADDITIONAL_SOURCES=My.Application`
`92`	`92`
`93`		-See the :new-page:`OpenTelemetry official documentation <https://opentelemetry.io/docs/languages/net/instrumentation/#metrics` for additional information and examples.
	`93`	+See the :new-page:`OpenTelemetry official documentation <https://opentelemetry.io/docs/languages/net/instrumentation/#metrics>` for additional information and examples.
Original file line number	Diff line number	Diff line change
`@@ -861,3 +861,4 @@ To keep up to date with changes in the products, see the Splunk Observability Cl`
`861`	`861`	`:maxdepth: 3`
`862`	`862`
`863`	`863`	`Contribute to our documentation <get-started/contribute>`
	`864`	`+`