Merge branch 'main' into update-sqlquery-receiver-rst

Author: aurbiztondo-splunk

.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.`
+            })

_images/infrastructure/rate-limiting-mua.png

@@ -7,22 +7,21 @@
 Maximum number of metric time series processed in a signal
 *****************************************************************
 
-To maximize responsiveness when processing incoming metric data, Splunk Observability Cloud limits the number of :term:`metric time series` (MTS) processed in a signal
-(single plot line) on a chart or detector. If the total number of time series for the metric specified in your signal exceeds this limit, Splunk Observability Cloud displays
-an orange border around the MTS number. This border notifies you that the processed data reflects only a subset of the time series in the data.
+To maximize responsiveness when processing incoming metric data, Splunk Observability Cloud limits the number of :term:`metric time series` (MTS) processed in a signal (single plot line) on a chart, detector, or navigator. If the total number of time series for the metric specified in your signal exceeds this limit, Splunk Observability Cloud displays a message at the top of the chart, detector, or navigator. This message notifies you that the processed data reflects only a subset of the time series in the data.
 
-To ensure that your charts and detectors are processing all the time series in the data, apply as many filters as necessary to make the MTS number less than the maximum.
-You'll know you've succeeded when the orange outline around the MTS number and the message at the top of the chart or detector no longer appear.
+To ensure that your charts, detectors, and navigators are processing all the time series in the data, apply as many filters as necessary to make the MTS number less than the maximum. You'll know you've succeeded when the message at the top of the chart, detector, or navigator no longer appears.
 
-For example, suppose you want to display the sum of available disk capacity per availability zone. You might use ``df.complex.free`` as your signal,
-then apply the Sum analytics function, grouped by availability zone. If you have a large number of disks, the number of MTS returned by this signal might
+For example, suppose you want to display the sum of available disk capacity per availability zone. You might use ``df.complex.free`` as your signal, then apply the Sum analytics function, grouped by availability zone. If you have a large number of disks, the number of MTS returned by this signal might
 exceed the limit. To reduce the number of MTS, use filters and multiple plots instead of the group-by option in the Sum analytics function.
 
+Use filters and multiple plots on charts and detectors
+========================================================
+
 To use filters and multiple plots instead of the group-by option, follow these steps:
 
 #. Apply a filter for the plot that selects a single availability zone, then use the Sum analytic function without the group-by option.
 #. At the end of the plot row, select :guilabel:`Configure plot` to open :guilabel:`Visualization Options`, then select a color from :guilabel:`Plot Color`.
-#. Clone the plot. To do this, open the :guilabel:`plot actions` menu at the end of the plot row in the :guilabel:`Plot Editor`,
+#. Clone the plot. To do this, open the :guilabel:`Plot actions` menu at the end of the plot row in the :guilabel:`Plot Editor`,
    then select :menuselection:`Clone`.
 #. In the cloned plot, change the availability zone filter to select another availability zone, and change the :guilabel:`Plot Color` to give the cloned
    plot a color that's different from the original plot.
@@ -31,3 +30,8 @@ To use filters and multiple plots instead of the group-by option, follow these s
 The result is one chart with a separate plot line for each availability zone. Each plot line has a distinct color.
 
 For more information on filtering, see :ref:`filter-signal`.
+
+Use filters on navigators
+=============================
+
+To use filters on navigators, see :ref:`add-filter`.

_images/synthetics/auth-multifactor-totp-add-variable.png

@@ -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%;">

_images/synthetics/auth-multifactor-totp-fillinfield.png

@@ -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%;">

_images/synthetics/auth-multifactor-totp-trynow.png

@@ -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%;">

_includes/chart-mts-count.rst

@@ -24,8 +24,8 @@ send data to Infrastructure Monitoring.
 
 When a host uses the token to send data, Infrastructure Monitoring compares the
 token limits to all hosts' cumulative resource usage that use the token. When cumulative
-resource usage exceeds the limit, Infrastructure Monitoring issues an alert and
-stops ingesting data sent by hosts using the token.
+resource usage exceeds the limit, Infrastructure Monitoring issues an alert but continues
+ingesting data for some time. If this continued ingestion causes a system overage, contact Support. See :ref:`support`.
 
 Because the limits for one access token don't affect limits for other access tokens,
 you can set different limits for different types of hosts. For example, set high