Pulling refs/heads/main into main

apm/span-tags/cmms.rst

@@ -134,7 +134,7 @@ Follow these steps to create a Monitoring MetricSet for an instrumented service:
 .. note:: For standard MMS Splunk APM replaces dots with underscores in dimension names for MMS time series. For histogram MMS underscores are preserved.
 .. _inferred-service-mms:
 
-Create a Monitoring MetricSet with a custom dimension for an inferred service
+Create a Monitoring MetricSet for an inferred service
 =======================================================================================
 
 .. note:: Only 3rd-party or uninstrumented HTTP services are supported for MMS.

apm/span-tags/metricsets.rst

@@ -57,7 +57,7 @@ MMS are available for the APM components listed in the following table. Each MMS
        * ``service.name`` - This dimension is only available for histogram MMS.
        * ``sf_error``
      - Yes
-   * - ``inferred.services`` - 
+   * - ``inferred.services`` - the requests to a service that has not yet been instrumented
      - * ``sf_service``
        * ``service.name`` - This dimension is only available for histogram MMS.
        * ``sf_environment``

data-visualization/charts/chart-options.rst

@@ -217,8 +217,26 @@ When data is sampled, you can see a message like this on the chart:
 .. image:: /_images/images-charts/sampling.png
     :width: 65%
 
-If you click :guilabel:`Click here to disable sampling`, or check the :guilabel:`Disable sampling` checkbox in the chart options tab, the sampling message is no longer displayed, and any time series data previously omitted is shown. Depending on the number of time series, disabling sampling might cause the chart to render more slowly.
+If you select :guilabel:`Click here to disable sampling`, or select the :guilabel:`Disable sampling` check box in the chart options tab, the sampling message is no longer displayed, and any time series data previously omitted is shown. Depending on the number of time series, disabling sampling might cause the chart to render more slowly.
 
+.. _chart-drilldown-link:
+
+Drilldown link
+=============================================================================
+
+This option lets you add a drilldown link to the chart header when you view the chart in a dashboard.
+
+.. image:: /_images/images-charts/charts-drilldown-link.png
+    :width: 65%
+
+Providing a drilldown link helps other users in your organization navigate to other parts of Splunk Observability Cloud or external resources containing data related to the chart.
+
+You can include dashboard variables and time range in the URL using curly brackets, such as ``startTime={{{-15m}}}``. For more information on dashboard variables, see :ref:`customize-dashboard-variables`.
+
+For example, you can configure a link to go from a chart to a RUM instance during a specific time window for the same metric.
+
+.. image:: /_images/images-charts/drilldown-example.png
+    :width: 65%
 
 .. _heatmap-group-by:
 
@@ -258,7 +276,7 @@ Max delay
 
 By default, the :strong:`Max delay` field is set to ``Auto``, which allows data to come in with as little delay as possible.
 
-If you know that some of your data is delayed and you want to wait for that data to arrive before your charts are updated, click the drop-down menu and choose a new value from the list. For more information, see :ref:`delayed-datapoints`.
+If you know that some of your data is delayed and you want to wait for that data to arrive before your charts are updated, select the dropdown menu and select a new value from the list. For more information, see :ref:`delayed-datapoints`.
 
 The value you specify is applied whenever you open the chart or view it in a dashboard, unless there is a max delay override. To learn more, see :ref:`dashboard-max-delay`.
 
@@ -321,7 +339,7 @@ To learn more about rollups, see :ref:`rollups`.
 No active metrics message
 =============================================================================
 
-This option allows you to add an optional message on graph charts, heatmap charts, list charts, and single value charts to indicate when metrics used in a chart either don't exist or are inactive. 
+This option lets you add an optional message on graph charts, heatmap charts, list charts, and single value charts to indicate when metrics used in a chart either don't exist or are inactive. 
 
 A metric is considered inactive by Splunk Observability Cloud in the following cases: 
 

data-visualization/dashboards/dashboard-create-customize.rst

@@ -95,8 +95,7 @@ Customizing mirrored dashboard filters
 Customize dashboard variables
 =========================================
 
-You can define various dashboard variable settings that take effect for any dashboard in this dashboard group.
-Select :guilabel:`Dashboard Variables` from the dashboard's Actions menu.
+You can define various dashboard variable settings that take effect for any chart in this dashboard. Select :guilabel:`Dashboard variables` from the dashboard actions menu.
 
 When you save these settings, the dashboard variable and the suggested values now reflect the customizations you
 specified.
@@ -105,12 +104,12 @@ Customizing mirrored dashboard variables
 ----------------------------------------
 
 - You can make changes directly on the :guilabel:`Overrides` bar; if you save the mirror, these settings become
-  default values in the :guilabel:`Variable Details` section of the :guilabel:`Dashboard Variables` tab.
+  default values in the :guilabel:`Variable details` section of the :guilabel:`Dashboard variables` tab.
 
-- When you save customization options that you set in the :guilabel:`Dashboard Variables` tab, these changes are
+- When you save customization options that you set in the :guilabel:`Dashboard variables` tab, these changes are
   automatically saved as default settings for this mirror.
 
-- On the :guilabel:`Dashboard Variables` tab, anyone with dashboard write permissions can add, delete, and edit
+- On the :guilabel:`Dashboard variables` tab, anyone with dashboard write permissions can add, delete, and edit
   dashboard variables and their settings. These variables affect all mirrors that don't have variable
   customizations applied.
 

gdi/opentelemetry/collector-linux/collector-linux-intro.rst

@@ -48,7 +48,7 @@ To install the Splunk Distribution of the OpenTelemetry Collector for Linux you
 See the default settings and configuration options at:
 
 * :ref:`linux-config-ootb`
-* By default, you'll obtain these :ref:`metrics <ootb-metrics-windows>` 
+* By default, you'll obtain these :ref:`metrics <ootb-metrics-linux>` 
 * :ref:`otel-linux-config`
 * :ref:`linux-config-logs`
 

gdi/opentelemetry/data-processing.rst

@@ -7,7 +7,7 @@ Process your data with pipelines
 .. meta::
       :description: Learn how to process data collected with the Splunk Distribution of the OpenTelemetry Collector.
 
-Use pipelines in your Collector's config file to define the path you want your ingested data to follow. Specify which components you want to use, starting from data reception using :ref:`receivers <otel-components-receivers>`, then data processing or modification with :ref:`processors <otel-components-processors>`, until data finally exits the Collector through :ref:`exporters <otel-components-exporters>`. For an overview of all available components and their behavior refer to :ref:`otel-components`.
+Use pipelines in your Collector's config file to define the path you want your ingested data to follow. Specify which components you want to use, starting from data reception using :ref:`receivers <otel-components-receivers>`, then data processing or modification with :ref:`processors <otel-components-processors>`, until data finally exits the Collector through :ref:`exporters <otel-components-exporters>`. For an overview of all available components and their behavior refer to :ref:`otel-components`. For general recommendations and guidelines for using processors, see the :new-page:`OpenTelemetry processor documentation <https://github.com/open-telemetry/opentelemetry-collector/tree/main/processor#recommended-processors>`.   
 
 Pipelines operate on three data types: logs, traces, and metrics. To learn more about data in Splunk Observability Cloud, see :ref:`data-model`.
 

gdi/opentelemetry/otel-other/telegraf.rst

@@ -39,7 +39,7 @@ Follow these steps to scrape Telegraf metrics with the OTel Collector:
 3. Set up the Telegraf OpenTelemetry Output plugin
 4. Configure the OpenTelemetry Collector
 
-5. Install Telegraf 
+1. Install Telegraf 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Run the following commands to install Telegraf from the InfluxData repository: