Pulling refs/heads/main into main

_includes/metric-classes.rst

@@ -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

_includes/synthetics/chrome-flags.rst

@@ -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. 
+

_includes/zero-code-info.rst

@@ -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`.
+

alerts-detectors-notifications/alerts-and-detectors/create-detectors-for-alerts.rst

@@ -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:
 

apm/span-tags/tag-spotlight.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
 ----------------------------------------------------------------------
 

data-visualization/charts/chart-builder.rst

@@ -19,7 +19,7 @@ If you are editing an existing chart, you might want to start by configuring plo
 Specify a signal for a plot line
 =============================================================================
 
-A signal is the :term:`metric` or :ref:`histogram metric <histograms>` you want to plot on the chart, to which you might add filters and apply analytics. Plot lines, or plots, are the building blocks of charts. A chart has one or more plots, and each plot is composed of the :term:`metric time series<Metric time series>` or histogram metric represented by the signal and its properties and dimensions, any filters, and any analytics applied.
+A signal is the :term:`metric` or :ref:`histogram metric <histograms>` you want to plot on the chart, to which you might add filters and apply analytics. Plot lines, or plots, are the building blocks of charts. A chart has one or more plots, and each plot is composed of the :term:`metric time series<metric time series>` or histogram metric represented by the signal and its properties and dimensions, any filters, and any analytics applied.
 
 .. note:: Instead of a metric, you can also enter a :ref:`time series expression<expression>` to create a composite or derived metric, specify an :ref:`event<chart-events>` to be displayed on the chart, or :ref:`link a detector to a chart<link-detector-to-chart>` to display its alert status on the chart.
 
@@ -114,6 +114,17 @@ In this case, if you want to plot a metric as histogram, do the following steps
 
 For more information on histogram function and supported methods, see :new-page:`histogram() <https://dev.splunk.com/observability/docs/signalflow/functions/histogram_function>` in the SignalFlow reference documentation.
 
+.. _archived-metrics-charts:
+
+Use archived metrics in charts
+--------------------------------------
+
+When you select an archived metric as a signal in your chart, the archived metric can't be plotted.
+
+To include an archived metric in a chart, route the archived metric to real-time or create exception rules to make it available. For more information, see the :ref:`mpm-rule-routing-exception` section.
+
+To learn more about MPM, see :ref:`metrics-pipeline-intro`.
+
 .. _filter-signal:
 
 Filter the signal

gdi/get-data-in/application/application.rst

@@ -19,6 +19,7 @@ Instrument back-end applications to send spans to Splunk APM
    Instrument a PHP application TOGGLE <php/get-started>
    Instrument a C++ application TOGGLE <cpp/get-started-cpp>
    Send spans from the Istio service mesh <istio/istio>
+   Instrumentation methods <zero-code-overview>
 
 You can instrument your back-end services and applications to send metrics and traces to Splunk Observability Cloud.
 

gdi/get-data-in/application/go/instrumentation/instrument-go-application.rst

@@ -7,6 +7,8 @@ Instrument your Go application for Splunk Observability Cloud
 .. meta::
    :description: The Splunk Distribution of OpenTelemetry Go can instrument your Go application or service. Follow these steps to get started.
 
+.. include:: /_includes/zero-code-info.rst
+
 The Splunk Distribution of OpenTelemetry Go can instrument your Go application or service. To get started, use the guided setup or follow the instructions manually.
 
 Generate customized instructions using the guided setup

gdi/get-data-in/application/java/instrumentation/instrument-java-application.rst

@@ -9,6 +9,8 @@ Instrument your Java application for Splunk Observability Cloud
 
 The Java agent from the Splunk Distribution of OpenTelemetry Java can automatically instrument your Java application by injecting instrumentation to Java classes. To get started, use the guided setup or follow the instructions manually.
 
+.. include:: /_includes/zero-code-info.rst
+
 Generate customized instructions using the guided setup
 ====================================================================
 

gdi/get-data-in/application/nodejs/instrumentation/instrument-nodejs-application.rst

@@ -7,6 +7,8 @@ Instrument your Node.js application for Splunk Observability Cloud
 .. meta::
    :description: The Splunk Distribution of OpenTelemetry Node.js can automatically instrument your Node.js application or service. Follow these steps to get started.
 
+.. include:: /_includes/zero-code-info.rst
+
 The Splunk Distribution of OpenTelemetry JS can automatically instrument your Node.js application and many of the popular node.js libraries your application uses.
 
 To get started, use the guided setup or follow the instructions manually.

gdi/get-data-in/application/otel-dotnet/get-started.rst

@@ -25,7 +25,7 @@ Instrument .NET applications for Splunk Observability Cloud (OpenTelemetry)
    SignalFx Instrumentation for .NET (Deprecated) TOGGLE <sfx/sfx-instrumentation>
    Migrate from SignalFx Instrumentation for .NET <troubleshooting/migrate-signalfx-dotnet-to-dotnet-otel>
 
-The Splunk Distribution of OpenTelemetry .NET provides automatic instrumentation for popular .NET libraries and frameworks to collect and send telemetry to Splunk Observability Cloud.
+The Splunk Distribution of OpenTelemetry .NET provides zero-code instrumentation for popular .NET libraries and frameworks to collect and send telemetry to Splunk Observability Cloud.
 
 .. raw:: html
 

gdi/get-data-in/application/otel-dotnet/instrumentation/dotnet-pre-checks.rst

@@ -5,9 +5,9 @@ Pre-checks
 **********
 
 .. meta::
-    :description: A list of pre-checks for the user to complete before installing the .NET automatic instrumentation.
+    :description: A list of pre-checks for the user to complete before installing the .NET zero-code instrumentation agent.
 
-Before installing the .NET automatic instrumentation, complete the following pre-checks.
+Before installing the .NET zero-code instrumentation agent, complete the following pre-checks.
 
 Verify platform compatibility
 =============================
@@ -57,7 +57,7 @@ Review core dependencies
 
 Make sure that your application's dependencies are compatible with the .NET instrumentation.
 
-#. Verify whether your target applications have the same dependencies as the automatic instrumentation. See :new-page:`OpenTelemetry.AutoInstrumentation <https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/src/OpenTelemetry.AutoInstrumentation/OpenTelemetry.AutoInstrumentation.csproj>` and :new-page:`OpenTelemetry.AutoInstrumentation.AdditionalDeps <https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/src/OpenTelemetry.AutoInstrumentation.AdditionalDeps/Directory.Build.props>`. If there are conflicts, consider installing using the NuGet packages. Otherwise, you must resolve all the dependencies before manually installing the instrumentation.
+#. Verify whether your target applications have the same dependencies as the zero-code instrumentation. See :new-page:`OpenTelemetry.AutoInstrumentation <https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/src/OpenTelemetry.AutoInstrumentation/OpenTelemetry.AutoInstrumentation.csproj>` and :new-page:`OpenTelemetry.AutoInstrumentation.AdditionalDeps <https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/src/OpenTelemetry.AutoInstrumentation.AdditionalDeps/Directory.Build.props>`. If there are conflicts, consider installing using the NuGet packages. Otherwise, you must resolve all the dependencies before manually installing the instrumentation.
 
 #. Verify whether your target applications have the same dependencies as the NuGet packages. See the :new-page:`NuGet dependencies <https://www.nuget.org/packages/OpenTelemetry.AutoInstrumentation/#dependencies-body-tab>` in the NuGet documentation. If there are conflicts, you must resolve them before installing the instrumentation using the NuGet packages.