Merge pull request #1601 from splunk/repo-sync

Pulling refs/heads/main into main

Author: aurbiztondo-splunk

_images/images-metrics/usage-analytics-example-profile.png

@@ -0,0 +1,28 @@
+.. list-table:: 
+  :header-rows: 1
+  :widths: 20 80
+  :width: 100%
+
+  * - :strong:`Billing class`
+    - :strong:`Metrics included`
+  * - Custom metrics
+    - Metrics reported to Splunk Observability Cloud outside of those reported by default, such as host, container, or bundled metrics. Custom metrics might result in increased data ingest costs.
+  * - APM Monitoring MetricSets
+    - Includes metrics from APM Monitoring MetricSets. See :ref:`apm-metricsets` for more information.
+  * - RUM Monitoring MetricSets
+    - Includes metrics from RUM Monitoring MetricSets. See :ref:`rum-custom-indexed-tags` for more information.
+  * - Default/bundled metrics (Infrastructure)
+    - * Host
+      * Container
+      * Bundled
+      * Additional metrics sent through infrastructure monitoring public cloud integrations that aren't attributed to specific hosts or containers.
+  * - Default/bundled metrics (APM)
+    - * Host
+      * Container
+      * Identity
+      * Bundled
+      * Tracing 
+      * Runtime
+      * Synthetics
+  * - Other metrics
+    - Internal metrics

_images/images-metrics/usage-analytics-home-page.png

@@ -0,0 +1,22 @@
+.. list-table::
+  :header-rows: 1
+  :widths: 40 60
+  :width: 100%
+
+  * - :strong:`Chrome flag`  
+    - :strong:`Description`
+  * - ``--disable-http2``
+    - Requests are made using using ``http/1.1`` instead of ``http/2.0``. This HTTP version is viewable in the HAR file.
+  * - ``--disable-quic``
+    - Deactivates QUIC, which also deactivates HTTP3.
+  * - ``--disable-web-security``
+    - Deactivate enforcement of same origin policy.
+  * - ``--unsafely-treat-insecure-origin-as-secure=http://a.test,http://b.test``
+    - Treat given insecure origin as secure. Multiple origins can be supplied in a comma-separated list.
+  * - ``--proxy-bypass-list="*.google.com;*foo.com;127.0.0.1:8080"``
+    - Proxy bypass list for any specified proxy for the given semi-colon-separated list of hosts. This flag must be used with ``--proxy-server``.
+  * - ``--proxy-server="foopy:8080"``
+    - Uses a specified proxy server to override default settings.
+  * - ``--no-proxy-server``
+    - Don't use a proxy server, always make direct connections. This flag can be used to override any other proxy server flags that you may have set up in a private location. 
+

_images/synthetics/Synth-built-in-dashboards.png

@@ -0,0 +1,2 @@
+.. note:: Due to changes in the upstream OpenTelemetry documentation, "automatic instrumentation" has been changed to "zero-code instrumentation". For more information, see :ref:`zero-code-overview`.
+

_images/synthetics/ootb-dashboard-modal.png

@@ -115,11 +115,15 @@ Select alert signals
 
 On the :strong:`Alert signal` tab, define the signal to monitor by entering a metric and corresponding analytics.
 
-If you are creating a detector from scratch, you have to first select the signals you want to monitor. Selecting a signal for a detector is similar to selecting a signal in a chart in the Chart Builder. Enter a metric and select the metric you want to monitor from the list. Add filters or analytics. To learn more, see :ref:`specify-signal`.
+* If you are creating a detector from scratch, you have to first select the signals you want to monitor. Selecting a signal for a detector is similar to selecting a signal in a chart in the Chart Builder. Enter a metric and select the metric you want to monitor from the list. Add filters or analytics. To add more signals, select :guilabel:`Add Metric or Event` or :guilabel:`Add Formula`. You can add events to be displayed on the chart, but you cannot select an event as the signal to be monitored. To learn more, see :ref:`specify-signal`.
 
-If you want to add more signals, select :guilabel:`Add Metric or Event` or :guilabel:`Add Formula`. Note that you can add events to be displayed on the chart, but you cannot select an event as the signal to be monitored.
 
-.. note:: If you are creating a detector :ref:`from a chart<create-detector-from-chart>` or by :ref:`cloning a detector<clone-detector>`, you might not need to add new signals. However, if you do add new signals to the detector, the signals you add are not added to the original chart or detector.
+   .. note:: When you select an archived metric as a signal in your detector, the archived metric can't be report data to your detector and will cause the detector to misfire alerts or stop working. To include an archived metric in detectors, route them to real-time or create exception rules to make them available. For more information, see the :ref:`mpm-rule-routing-exception` section.
+
+* If you are creating a detector :ref:`from a chart<create-detector-from-chart>` or by :ref:`cloning a detector<clone-detector>`, you might not need to add new signals. However, if you do add new signals to the detector, the signals you add are not added to the original chart or detector.
+
+* You can add events to be displayed on the chart, but you can't select an event as the signal to be monitored.
+
 
 .. _compound-conditions:
 

_includes/metric-categories.rst

@@ -31,6 +31,14 @@ To view service performance broken down by your indexed span tags, follow these
 #. View the distribution of all indexed span tags. The tag bar charts display either request and error distributions or latency distribution. Use the :guilabel:`Cards display` menu to select the data you want to display in the bars. 
 #. Select the menu on the top left of the bar chart section to select which metrics to display in each tag panel. You can also use this menu to select whether to display tags with no values.
 
+Customize tags display on Tag Spotlight    
+----------------------------------------------------------------------
+To configure the layout of the cards on the Tag Spotlight page, follow these steps: 
+
+#. From the menu on the top left of the bar chart, select :guilabel:`Customize card display order`. 
+#. Drag each of the span tags to arrange the order that cards are displayed on the page. Arrange the tags by priority, order of importance, or other criteria.
+#. Select :guilabel:`Save`. 
+
 Explore the distribution of span tags and values to find trends
 ----------------------------------------------------------------------