Fixes

Author: aurbiztondo-splunk

gdi/integrations-list.rst

@@ -20,7 +20,7 @@ Supported integrations in Splunk Observability Cloud
   APM instrumentation <get-data-in/application/application>
   RUM instrumentation <get-data-in/rum/rum-instrumentation>  
   OpenTelemetry: Receivers <opentelemetry/components/a-components-receivers>
-  OpenTelemetry: Other ingestion methods
+  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>

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/opentelemetry/otel-other/otel-other-landing.rst

@@ -1,7 +1,7 @@
 .. _otel-other-landing:
 
 ******************************************
-Collector components: Receivers
+Other OpenTelemetry ingestion methods
 ******************************************
 
 .. meta::
@@ -13,7 +13,7 @@ Collector components: Receivers
     :hidden:
 
     prometheus-generic
-    telegraf-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:
 

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`