Merge branch 'main' into tcarter-OD6463-WorkRule

Author: Tracey Carter

gdi/monitors-databases/exec-input.rst

@@ -1,12 +1,18 @@
 .. _exec-input:
 
-Exec Input
-==========
+Exec Input (deprecated)
+==============================
 
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the Telegraf Exec monitor. See benefits, install, configuration, and metrics
 
-The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
+.. caution:: 
+   
+   The Exec Input monitor is now deprecated and will reach of End of Support on February 3, 2025. During this period only critical security and bug fixes are provided. When End of Support is reached, the monitor will be removed and no longer be supported, and you won't be able to use it to send data to Splunk Observability Cloud. 
+
+   To monitor your system with Telegraf Exec you can use native OpenTelemetry instead. See more at :new-page:`OpenTelemetry Output Plugin <https://github.com/influxdata/telegraf/blob/master/plugins/outputs/opentelemetry/README.md>` in GitHub. 
+
+The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the
 Exec Input monitor type, an embedded form of the Telegraf Exec plugin,
 to receive metrics or logs from exec files.
 

gdi/monitors-databases/mysql.rst

@@ -12,7 +12,7 @@ MySQL (deprecated)
 
    To monitor your MySQL databases you can use the native OpenTelemetry MySQL receiver instead. See more at :ref:`MySQL receiver <mysql-receiver>`. 
 
-The :ref:`Splunk Distribution of OpenTelemetry Collector <otel-intro>` uses the :ref:`Smart Agent receiver <smartagent-receiver>` with the MySQL monitor type to retrieve metrics and logs from MySQL.
+The :ref:`Splunk Distribution of the OpenTelemetry Collector <otel-intro>` uses the :ref:`Smart Agent receiver <smartagent-receiver>` with the MySQL monitor type to retrieve metrics and logs from MySQL.
 
 This monitor connects to a MySQL instance and reports on the values
 returned by a ``SHOW STATUS`` command, which include the following:

gdi/monitors-monitoring/nagios.rst

@@ -1,12 +1,18 @@
 .. _nagios:
 
-Nagios
-======
+Nagios (deprecated)
+==============================
 
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the nagios monitor. See benefits, install, configuration, and metrics
 
-The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
+.. caution:: 
+   
+   The Nagios monitor is now deprecated and will reach of End of Support on October 31st, 2024. During this period only critical security and bug fixes are provided. When End of Support is reached, the monitor will be removed and no longer be supported, and you won't be able to use it to send data to Splunk Observability Cloud. 
+
+   To monitor your system you can use native OpenTelemetry components instead. See more at :ref:`otel-components`. 
+
+The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the
 Nagios monitor type to run existing Nagios status check scripts through
 the Collector, which acts as the Nagios Remote Plugin Executor (NRPE) or
 the Simple Network Management Protocol (SNMP) exec directive, and send

gdi/opentelemetry/components/host-metrics-receiver.rst

@@ -205,7 +205,26 @@ Process
      mute_process_io_error: <true|false>
      scrape_process_delay: <time>
 
-If you keep getting errors related to process reading, consider setting ``mute_process_name_error``, ``mute_process_exe_error``, or ``mute_process_io_error`` to ``true``.
+The following example demonstrates how to configure a process scraper that collects two metrics, in addition to the defaults, and uses a resource attribute to include the process owner in the collected data:
+
+.. code:: yaml
+
+   receivers:
+     hostmetrics:
+       scrapers:
+         process:
+           resource_attributes:
+             process.owner:
+               enabled: true
+           metrics:
+             process.memory.usage:
+               enabled: true
+             process.disk.io:
+               enabled: true
+
+For more information about enabling and disabling metrics and resource attributes using the process scraper, see :new-page:`hostmetricsreceiver/process <https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/hostmetricsreceiver/internal/scraper/processscraper/documentation.md>` in the OpenTelemetry documentation.
+
+If you continuously see errors related to process reading, consider setting ``mute_process_name_error``, ``mute_process_exe_error``, or ``mute_process_io_error`` to ``true``.
 
 Filtering
 ----------------------