Merge pull request #2478 from splunk/urbiz-OD6512-telegraf-links

[6512]: Telegraf links

gdi/integrations-list.rst

@@ -19,7 +19,8 @@ Supported integrations in Splunk Observability Cloud
   Infrastructure monitoring <get-data-in/compute/compute>
   APM instrumentation <get-data-in/application/application>
   RUM instrumentation <get-data-in/rum/rum-instrumentation>  
-  OpenTelemetry receivers <opentelemetry/components/a-components-receivers>
+  OpenTelemetry: Receivers <opentelemetry/components/a-components-receivers>
+  OpenTelemetry: Other ingestion methods <opentelemetry/otel-other/otel-other-landing>
   Applications: Caches and memory TOGGLE <caches-memory>
   Applications: Cloud platforms TOGGLE <cloud>
   Applications: Cloudfoundry <monitors-cloudfoundry/cloudfoundry-firehose-nozzle>
@@ -130,6 +131,7 @@ You can monitor your applications and services with the Collector and the follow
 You can also send data to Splunk Observability Cloud with OpenTelemetry with the following options:
 
 * :ref:`prometheus-generic`
+* :ref:`telegraf-generic`
 
 .. raw:: html
 

gdi/monitoring.rst

@@ -13,11 +13,9 @@ Configure application exporters and receivers for monitoring
 
    monitors-monitoring/cadvisor
    monitors-monitoring/cgroups
-   Istio <get-data-in/application/istio/istio>
    monitors-monitoring/jaeger-grpc
    monitors-monitoring/nagios
    monitors-monitoring/signalfx-forwarder
-   opentelemetry/components/splunk-apm-exporter
    monitors-monitoring/win_perf_counters
 
 These application receivers gather metrics from their associated monitoring applications and the hosts the applications are running on.
@@ -28,7 +26,6 @@ These application receivers gather metrics from their associated monitoring appl
 * :ref:`jaeger-grpc`
 * :ref:`nagios`
 * :ref:`signalfx-forwarder`
-* :ref:`telegraf`
 * :ref:`telegraf-win-perf-counters`
 
 These exporters determine where to send the received data.

gdi/monitors-databases/exec-input.rst

@@ -10,11 +10,9 @@ 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 more at :new-page:`OpenTelemetry Output Plugin <https://github.com/influxdata/telegraf/blob/master/plugins/outputs/opentelemetry/README.md>` in GitHub. 
+   To monitor your system with Telegraf Exec you can use native OpenTelemetry instead. See :ref:`telegraf-generic` to learn how.
 
-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.
+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.
 
 Benefits
 --------

gdi/opentelemetry/otel-other/otel-other-landing.rst

@@ -0,0 +1,21 @@
+.. _otel-other-landing:
+
+******************************************
+Other OpenTelemetry ingestion methods
+******************************************
+
+.. meta::
+    :description: Learn about other options to send your data with OpenTelemetry to Splunk Observability Cloud OpenTelemetry Collector.
+
+.. toctree::
+    :maxdepth: 4
+    :titlesonly:
+    :hidden:
+
+    prometheus-generic
+    telegraf
+
+On top of the available native :ref:`OpenTelemetry receivers <otel-components-receivers>`, you can also send data to Splunk Observability Cloud with OpenTelemetry with the following options:
+
+* :ref:`prometheus-generic`
+* :ref:`telegraf-generic`

gdi/monitors-monitoring/telegraf.rst → gdi/opentelemetry/otel-other/telegraf.rst

@@ -1,4 +1,5 @@
 .. _telegraf:
+.. _telegraf-generic:
 
 Monitor services with Telegraf and OpenTelemetry
 ========================================================

gdi/prometheus.rst

@@ -11,24 +11,21 @@ Configure application receivers with Prometheus metrics
    :maxdepth: 4
    :hidden:
 
-   monitors-prometheus/prometheus-generic
-   opentelemetry/components/prometheus-receiver
    monitors-prometheus/prometheus-exporter
    monitors-prometheus/prometheus-go
    monitors-prometheus/prometheus-nginx-ingress
    monitors-prometheus/prometheus-nginx-vts
    monitors-prometheus/prometheus-node
    monitors-prometheus/prometheus-velero
 
-You can use the OpenTelementry native Prometheus receiver to gather metrics from any software, tool or service that exposes metrics in the Prometheus format, such as Ansible Tower (AWX), CockroachDB, Docker Daemon, Doorman, Etcd, Flink, Grafana, PATROL, Traefik, or Zipkin. See more at :ref:`prometheus-receiver`.
+Splunk Observability Cloud offers the following OTel solutions to monitor applications and services that expose metrics in the Prometheus format:
 
-Splunk Observability Cloud offers the following solutions:
+* :ref:`prometheus-receiver`. You can use the OpenTelementry native Prometheus receiver to gather metrics from any software, tool or service that exposes metrics in the Prometheus format, such as Ansible Tower (AWX), CockroachDB, Docker Daemon, Doorman, Etcd, Flink, Grafana, PATROL, Traefik, or Zipkin. 
+* :ref:`prometheus-generic`.
 
-* :ref:`prometheus-generic`
-* :ref:`prometheus-receiver`
-* See a complete list of third-party applications compatible with Prometheus in :new-page:`Prometheus' official documentation <https://prometheus.io/docs/instrumenting/exporters/>`. 
+You can find the complete list of third-party applications compatible with Prometheus in :new-page:`Prometheus' official documentation <https://prometheus.io/docs/instrumenting/exporters/>`. 
 
-See also:
+The following Smart Agent monitors are also available:
 
 * :ref:`prometheus-exporter`
 * :ref:`prometheus-go`