Merge branch 'main' into tcarter-OD6300-Detectors

Author: Tracey Carter

_includes/gdi/available-aws.rst

@@ -447,6 +447,13 @@ You can collect data from the following AWS services:
     - :strong:`X`
     - :strong:`X`
 
+  * - AWS/NetworkFirewall
+    - AWS Network Firewall 
+    - :strong:`X`
+    - 
+    - 
+    - :strong:`X`
+
   * - AWS/OpsWorks
     - AWS OpsWorks
     - :strong:`X`

_includes/requirements/go.rst

@@ -1 +1 @@
-The Splunk Distribution of OpenTelemetry Go is compatible with Go 1.21 and higher.
+The Splunk Distribution of OpenTelemetry Go is compatible with Go 1.22 and higher.

_includes/troubleshooting-components.rst

@@ -2,7 +2,7 @@ If you are a Splunk Observability Cloud customer and are not able to see your da
 
 :strong:`Available to Splunk Observability Cloud customers`
 
-- Submit a case in the :new-page:`Splunk Support Portal <https://splunkcommunities.force.com/customers/home/home.jsp>`.
+- Submit a case in the :new-page:`Splunk Support Portal <https://splunk.my.site.com/customer/s/>`.
 
 - Contact :new-page:`Splunk Support <https://www.splunk.com/en_us/about-splunk/contact-us.html>`.
 

_templates/404.html

@@ -204,8 +204,8 @@ <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 Inc. 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 Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.</div>
+      <span style="color:black">&copy; 2005 - 2023 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%;">
         <a href="#feedbackModal" class="feedbackbtn">Feedback</a>

_templates/layout.html

@@ -206,8 +206,8 @@ <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 Inc. 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 Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.</div>
+      <span style="color:black">&copy; 2005 - 2023 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%;">
         <a href="#feedbackModal" class="feedbackbtn">Feedback</a>

_templates/search.html

@@ -268,8 +268,8 @@ <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 Inc. 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 Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.</div>
+        <span style="color:black">&copy; 2005 - 2023 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%;">
         <a href="#feedbackModal" class="feedbackbtn">Feedback</a>

admin/notif-services/servicenow.rst

@@ -35,15 +35,19 @@ Before you set up the integration, choose a ServiceNow issue type from the follo
       :width: 100
 
       * - Issue type
-        - Role needed
+        - Role required
+        - ServiceNow endpoint
       * - Problem
         - ``user_admin``, ``itil``
+        - ``/api/now/v2/table/problem``
       * - Incident
         - ``user_admin``, ``itil``
+        - ``/api/now/v2/table/incident``
       * - Event
         - None
+        - ``/api/global/em/jsonv2``
 
-Make note of the role that corresponds to your issue type before proceeding with :ref:`servicenow2`.
+Make note of the role and receiving endpoint that corresponds to your issue type before proceeding with :ref:`servicenow2`.
 
 .. note:: The ``user_admin`` role is used to verify that ServiceNow has successfully created a Problem or Incident. The ``itil`` role is used to create Problems and Incidents when alerts are sent. 
 

admin/references/system-limits/sys-limits-infra-details.rst

@@ -490,24 +490,6 @@ Container burst/overage limit
    * :strong:`Customer impact`: If you exceed this limit, Infrastructure Monitoring drops data points from new containers but keeps
      accepting data points for existing containers.
 
-.. _high-resolution-custom-metrics-entitlement:
-
-High resolution custom metrics entitlement
-================================================================================
-
-   * :strong:`Default limit value`: Set by your contract entitlement
-   * :strong:`Notes`: Number of high resolution metrics allowed in your contract
-   * :strong:`Customer impact`: Splunk charges an overage of 1.5 times the normal price for usage that exceeds your contractual entitlement.
-
-.. _high-resolution-custom-metrics-burstoverage-limit:
-
-High resolution custom metrics burst/overage limit
-================================================================================
-
-   * :strong:`Default limit value`: Multiples of entitlement
-   * :strong:`Notes`: This limit is to protect the SaaS platform. It's typically a multiple of your contractual limit. For example, if you purchase 500 hosts, Infrastructure Monitoring might set limit to 800. The multiple decreases as your contractual limit increases.
-   * :strong:`Customer impact`: The system rejects MTS creations for high resolution metrics that exceed the limit.
-
 .. _bundled-mts-limit:
 
 Bundled MTS limit

admin/references/system-limits/sys-limits-infra.rst

@@ -252,12 +252,6 @@ Subscription limits
    * - :ref:`custom-mts-entitlement`
      - Set by your contract entitlement
 
-   * - :ref:`high-resolution-custom-metrics-burstoverage-limit`
-     - Multiples of entitlement
-
-   * - :ref:`high-resolution-custom-metrics-entitlement`
-     - Set by your contract entitlement
-
    * - :ref:`host-burstoverage-limit`
      - Multiples of entitlement
 

alerts-detectors-notifications/alert-condition-reference/heartbeat-check.rst

@@ -17,7 +17,7 @@ Heartbeat Check alerts when a signal has not reported for some time. This might
 Examples
 ============================================================================
 
-You have a detector that alerts you when the minimum number of logins being handled by each host goes below a specified value. If any host stops reporting, that detector isn't triggered if there is a problem. The Heartbeat Check condition notifies you if a host stops reporting.
+You have a detector that alerts you when the minimum number of logins being handled by each host goes below a specified value. If a host stops reporting, that detector isn't triggered if there is a problem. The Heartbeat Check condition notifies you if a host stops reporting, or if all hosts in a group stop reporting.
 
 
 Settings
@@ -35,7 +35,7 @@ Settings
 
    * - :strong:`Hasn't reported for`
      - Integer >= 1, followed by time indicator (s, m, h, d, w). For example, 30s, 10m, 2h, 5d, 1w.
-     - How long it's been since the signal last reported. Longer time periods result in lower sensitivity and potentially fewer alerts. If you specify a value for :guilabel:`Group by` (below), how long it's been since any member of the group stopped reporting.
+     - How long it's been since the signal last reported. Longer time periods result in lower sensitivity and potentially fewer alerts. If you specify a value for :guilabel:`Group by` (below), how long it's been since all members of the group stopped reporting.
 
    * - (optional) :strong:`Group by`
      - Dimension or property chosen from dropdown menu