Merge pull request #1529 from splunk/repo-sync

Pulling refs/heads/main into main

Author: aurbiztondo-splunk

gdi/integrations-list.rst

@@ -152,7 +152,7 @@ These are the available Smart Agent monitors:
       <h2>Notification services<a name="notification-services" class="headerlink" href="#notification-services" title="Permalink to this headline">¶</a></h2>
    </embed>
 
-These integrations let you send Splunk Observability Cloud alert notifications to the following third-party notification services:
+These integrations let you send Splunk Observability Cloud alert notifications to the following notification services:
 
 - Amazon EventBridge
 - BigPanda
@@ -163,6 +163,7 @@ These integrations let you send Splunk Observability Cloud alert notifications t
 - ServiceNow
 - Slack
 - Splunk On-Call
+- Splunk platform
 - Webhook
 - xMatters
 

gdi/monitors-monitoring/signalfx-forwarder.rst

@@ -4,11 +4,11 @@ SignalFx Forwarder (deprecated)
 ==================================
 
 .. meta::
-   :description: Use this Splunk Observability Cloud integration for the SignalFX forwarder receiver. See benefits, install, configuration, and metrics
+   :description: Use this Splunk Observability Cloud integration for the SignalFx forwarder. See benefits, install, configuration, and metrics
 
 .. note:: This integration is deprecated. If you're using the Splunk Distribution of the OpenTelemetry Collector and want to forward data to Splunk Observability Cloud, use the native OTLP receiver. See more at :new-page:`OTLP receiver <https://github.com/open-telemetry/opentelemetry-collector/tree/main/receiver/otlpreceiver>` GitHub documentation.
 
-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
 ``signalfx-forwarder`` monitor type to run an HTTP server that listens
 for data points and trace spans, and forward them to Splunk
 Observability Cloud. This integration supports the latest formats for

gdi/opentelemetry/exposed-endpoints.rst

@@ -39,7 +39,7 @@ See the table for a complete list of exposed ports and endpoints:
   * - ``http(s)://localhost:8006``
     - Fluent forward receiver
   * - ``http(s)://0.0.0.0:9080``
-    - Smart Agent receiver with :new-page:`SignalFx Forwarder <https://docs.splunk.com/Observability/gdi/signalfx-forwarder/signalfx-forwarder.html>` monitor type (deprecated)
+    - Smart Agent receiver with the :ref:`signalfx-forwarder`  
   * - ``http(s)://0.0.0.0:9411/api/[v1|v2]/spans``
     - Zipkin receiver supporting V1 and V2
   * - ``http(s)://0.0.0.0:9943``

gdi/opentelemetry/smart-agent/smart-agent-migration-monitors.rst

@@ -38,7 +38,7 @@ For each Smart Agent monitor you want to add to the Collector, add a ``smartagen
 
 Instead of using ``discoveryRule``, use the Collector receiver creator and observer extensions. See :ref:`receiver-creator-receiver` for more information.
 
-If you're using a SignalFx Forwarder monitor (deprecated), add it to both a ``traces`` and a ``metrics`` pipeline, and use a Sapm exporter and a SignalFx exporter, as each pipeline's exporter, respectively. See more on :ref:`exporters <collector-components-processors>`.
+If you're using a SignalFx Forwarder monitor (deprecated), add it to both a ``traces`` and a ``metrics`` pipeline, and use a SAPM exporter and a SignalFx exporter, as each pipeline's exporter, respectively. See more on :ref:`exporters <collector-components-processors>`.
 
 Configure the Smart Agent receiver 
 ------------------------------------------------------------