Merge pull request #2479 from splunk/urbiz-OD6469-telegraf-links

aurbiztondo-splunk · web-flow · commit 94269fd8b68a · 2024-12-04T08:09:42.000+01:00
[6469]: Linking Telegraf monitors
diff --git a/gdi/monitors-databases/exec-input.rst b/gdi/monitors-databases/exec-input.rst
@@ -10,7 +10,7 @@ Exec Input (deprecated)
    
    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 :ref:`telegraf-generic` to learn how.
+   To collect exec file data use the OpenTelemetry Collector and the :new-page:`Telegraf Exec Input plugin <https://github.com/influxdata/telegraf/tree/master/plugins/inputs/exec>`. See how in :ref:`telegraf-generic`.
 
 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.
 
diff --git a/gdi/monitors-databases/logparser.rst b/gdi/monitors-databases/logparser.rst
@@ -7,6 +7,8 @@ Logparser
    
    :description: Use this Splunk Observability Cloud integration for the telegraf/logparser plugin monitor. See benefits, install, configuration, and metrics.
 
+.. caution:: Smart Agent monitors are being deprecated. To tail log files use the OpenTelemetry Collector and the :new-page:`Telegraf Tail Input plugin <https://github.com/influxdata/telegraf/blob/master/plugins/inputs/tail/README.md>`. See how in :ref:`telegraf-generic`.
+
 The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the ``telegraf/logparser`` monitor type to tail log files.
 
 This integration is based on the Telegraf logparser plugin, and all
diff --git a/gdi/monitors-databases/sql.rst b/gdi/monitors-databases/sql.rst
@@ -6,7 +6,7 @@ SQL
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the SQL monitor. See benefits, install, configuration, and metrics
 
-.. note:: If you're using the Splunk Distribution of the OpenTelemetry Collector and want to collect SQL metrics, use the native OTel :ref:`sqlquery-receiver` component.
+.. caution:: Smart Agent monitors are being deprecated. To collect SQL metrics use the native OpenTelemetry :ref:`sqlquery-receiver` component.
 
 The SQL monitor gathers database usage metrics from SQL queries on your databases. It's available for Kubernetes, Windows, and Linux.
 
diff --git a/gdi/monitors-hosts/procstat.rst b/gdi/monitors-hosts/procstat.rst
@@ -6,7 +6,9 @@ procstat
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the procstat monitor. See benefits, install, configuration, and metrics
 
-The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
+.. caution:: Smart Agent monitors are being deprecated. To collect metrics about processes use the OpenTelemetry Collector and the :new-page:`Telegraf Procstat Input plugin <https://github.com/influxdata/telegraf/tree/master/plugins/inputs/procstat>`. See how in :ref:`telegraf-generic`.
+
+The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the
 ``procstat`` monitor type to collect metrics about processes.
 
 This integration is available for Kubernetes, Linux, and Windows.
diff --git a/gdi/monitors-hosts/win-services.rst b/gdi/monitors-hosts/win-services.rst
@@ -6,7 +6,9 @@ Windows Services
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the Telegraf Win_services monitor. See benefits, install, configuration, and metrics
 
-The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
+.. caution:: Smart Agent monitors are being deprecated. To collect Windows service data use the OpenTelemetry Collector and the :new-page:`Telegraf Windows Services Input plugin <https://github.com/influxdata/telegraf/tree/master/plugins/inputs/win_services>`. See how in :ref:`telegraf-generic`.
+
+The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the
 ``telegraf/win_services`` monitor type to ingest metrics about Windows
 services.
 
diff --git a/gdi/monitors-languages/asp-dot-net.rst b/gdi/monitors-languages/asp-dot-net.rst
@@ -12,6 +12,8 @@ ASP.NET (deprecated)
 
    To forward data from a .NET application to Splunk Observability Cloud use the :ref:`Splunk Distribution of OpenTelemetry .NET <get-started-dotnet-otel>` instead. 
 
+   To monitor Windows Performance Counters with native OpenTelemetry refer to :ref:`windowsperfcounters-receiver`.
+
 The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the
 ``aspdotnet`` monitor type to retrieve metrics for requests, errors,
 sessions, and worker processes from ASP.NET applications.
diff --git a/gdi/monitors-languages/microsoft-dotnet.rst b/gdi/monitors-languages/microsoft-dotnet.rst
@@ -6,9 +6,11 @@ Microsoft .NET (deprecated)
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the .NET (dotnet) apps monitor. See benefits, install, configuration, and metrics
 
-.. note:: This integration is deprecated and will be removed in February 2025. To forward data to Splunk Observability Cloud, use the Splunk Distribution of OpenTelemetry .NET. For a full list of collected metrics, refer to :ref:`dotnet-otel-metrics-attributes`. 
+.. caution:: 
+   
+   This integration is deprecated and will be removed in February 2025. To forward data to Splunk Observability Cloud, use the Splunk Distribution of OpenTelemetry .NET. For a full list of collected metrics, refer to :ref:`dotnet-otel-metrics-attributes`. 
 
-The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
+The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the
 ``dotnet`` monitor type to report metrics for .NET applications.
 
 This integration is only available on Windows.
diff --git a/gdi/monitors-network/dns.rst b/gdi/monitors-network/dns.rst
@@ -6,9 +6,9 @@ DNS Query Input
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the Telegraf DNS monitor. See benefits, install, configuration, and metrics
 
-The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
-DNS Query Input monitor type (an embedded form of the Telegraf DNS Query
-plugin) to collect DNS data.
+.. caution:: Smart Agent monitors are being deprecated. To collect DNS data use the OpenTelemetry Collector and the :new-page:`Telegraf DNS Query Input plugin <https://github.com/influxdata/telegraf/tree/master/plugins/inputs/dns_query>`. See how in :ref:`telegraf-generic`.
+
+You can use the Splunk Distribution of the OpenTelemetry Collector's Smart Agent receiver with the DNS Query Input monitor type (an embedded form of the Telegraf DNS Query plugin) to collect DNS data.
 
 Benefits
 --------
diff --git a/gdi/monitors-network/snmp.rst b/gdi/monitors-network/snmp.rst
@@ -6,7 +6,9 @@ SNMP agent
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the SNMP agent monitor. See benefits, install, configuration, and metrics
 
-The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the
+.. caution:: Smart Agent monitors are being deprecated. To collect data from SNMP agents use the OpenTelemetry Collector and the :new-page:`Telegraf SNMP Input plugin <https://github.com/influxdata/telegraf/tree/master/plugins/inputs/snmp>`. See how in :ref:`telegraf-generic`.
+
+The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the
 ``snmp`` monitor type to collect metrics from SNMP agents.
 
 This integration is available for Kubernetes, Windows, and Linux.
diff --git a/gdi/opentelemetry/otel-other/telegraf.rst b/gdi/opentelemetry/otel-other/telegraf.rst
@@ -1,14 +1,13 @@
 .. _telegraf:
 .. _telegraf-generic:
 
-Monitor services with Telegraf and OpenTelemetry
-========================================================
+Monitor services with Telegraf Input plugins and OpenTelemetry
+=====================================================================
 
 .. meta::
    :description: Use this Splunk Observability Cloud integration for the Telegraf monitor. See benefits, install, configuration, and metrics.
 
-To monitor your service with Telegraf using native OpenTelemetry in Splunk Observability Cloud, install the service's Telegraf plugin then push metrics to the Splunk Opentelemetry Collector
-via OTLP. 
+To monitor your service with Telegraf using native OpenTelemetry in Splunk Observability Cloud, install the service's Telegraf Input plugin then push metrics to the Splunk Opentelemetry Collector via OTLP. 
 
 .. note:: This setup is designed for a Linux Ubuntu OS but should be replicable on any machines running Linux OS with Debian flavor. These instructions might not work on other OS (MacOS/Windows). 
 
@@ -45,9 +44,9 @@ Run the following commands to install Telegraf from the InfluxData repository:
 2. Set up your service's Telegraf Input plugin
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Next, install the Telegraf Input plugin for the service you want to monitor. Available plugins include Chrony, Consul, Docker, Elasticsearch, Fluentd, GitHub, Jenkins, RabbitMQ or SQL. Find a complete list of Input plugins at :new-page:`Telegraf Input plugins <https://github.com/influxdata/telegraf/tree/master/plugins/inputs/exec>` in GitHub.
+Next, install the Telegraf Input plugin for the service you want to monitor. Available plugins include Chrony, Consul, Docker, Elasticsearch, Fluentd, GitHub, Jenkins, RabbitMQ or SQL. Find a complete list of available plugins at :new-page:`Telegraf Input plugins <https://github.com/influxdata/telegraf/tree/master/plugins/inputs>` in GitHub.
 
-For example, if you want to monitor execute commands on every interval and parse metrics from their output with the exec input plugin, use a setup like: 
+For example, if you want to monitor execute commands on every interval and parse metrics from their output with the Exec Input plugin, use a setup like: 
 
 .. code:: 
 
diff --git a/gdi/opentelemetry/smart-agent/smart-agent-migration-to-otel-collector.rst b/gdi/opentelemetry/smart-agent/smart-agent-migration-to-otel-collector.rst
@@ -25,7 +25,7 @@ Migrate from SignalFx Smart Agent to the Splunk Distribution of OpenTelemetry Co
    
    Smart Agent monitors are also being deprecated and will no longer be available to send data to Splunk Observability Cloud when they reach End of Support. Instead, you can use native OpenTelemetry receivers to gather data with the OTel Collector. See :ref:`migration-monitors-native`.
 
-The Splunk Distribution of the :new-page:`OpenTelemetry Collector <https://opentelemetry.io/docs/concepts/data-collection/>` provides a unified way to receive, process, and export metrics, traces, and logs to Splunk Observability Cloud. If you're using the SignalFx Smart Agent (deprecated) you can easily transition to the Collector without losing any functionality. 
+The Splunk Distribution of the OpenTelemetry Collector provides a unified way to receive, process, and export metrics, traces, and logs to Splunk Observability Cloud. If you're using the SignalFx Smart Agent (End Of Support) you must transition to the Collector. 
 
 .. raw:: html
 
