Removed SAPM

Author: aurbiztondo-splunk

_includes/collector-config-ootb.rst

@@ -165,15 +165,15 @@ The following diagram shows the default traces pipeline:
 
       subgraph Exporters
          direction LR
-         traces/sapm:::exporter
+         traces/otlphttp:::exporter
          traces/signalfx/out:::exporter
       end
 
       %% Connections beyond categories are added later
       traces/jaeger --> traces/memory_limiter
       traces/otlp --> traces/memory_limiter
       traces/zipkin --> traces/memory_limiter
-      traces/resourcedetection --> traces/sapm
+      traces/resourcedetection --> traces/otlphttp
       traces/resourcedetection --> traces/signalfx/out
 
 Learn more about these receivers:

apm/apm-spans-traces/span-formats.rst

@@ -16,13 +16,14 @@ For more information on the ingest API endpoints, see :new-page:`Send APM traces
 Span formats compatible with the OpenTelemetry Collector
 ================================================================
 
-The Splunk Distribution of the OpenTelemetry Collector can collect spans in the following format:
+The Splunk Distribution of the OpenTelemetry Collector can collect spans in the following formats:
 
 - Jaeger: gRPC and Thrift
 - Zipkin v1, v2 JSON
-- Splunk APM Protocol (SAPM)
 - OpenTelemetry Protocol (OTLP)
 
+.. note:: Splunk APM Protocol (SAPM) components are deprecated. Use the OTLP format instead.
+
 The following examples show how to configure receivers in the collector configuration file. You can use multiple receivers according to your needs.
 
 .. tabs::
@@ -51,14 +52,6 @@ The following examples show how to configure receivers in the collector configur
          zipkin:
             endpoint: 0.0.0.0:9411
 
-   .. code-tab:: yaml SAPM
-
-      # To receive spans in SAPM format
-
-      receivers:
-         sapm:
-            endpoint: 0.0.0.0:7276
-
    .. code-tab:: yaml OTLP
 
       # To receive spans in OTLP format
@@ -85,14 +78,12 @@ The ingest endpoint for Splunk Observability Cloud at ``https://ingest.<realm>.s
 * OTLP at ``/v2/trace/otlp`` with ``Content-Type:application/x-protobuf``
 * Jaeger Thrift with ``Content-Type:application/x-thrift``
 * Zipkin v1, v2 with ``Content-Type:application/json``
-* SAPM with ``Content-Type:application/x-protobuf``
 
 In addition, the following endpoints are available:
 
 * OTLP at ``/v2/trace/otlp`` with ``Content-Type:application/x-protobuf``
 * Jaeger Thrift at ``/v2/trace/jaegerthrift`` with ``Content-Type:application/x-thrift``
 * Zipkin v1, v2 at ``/v2/trace/signalfxv1`` with ``Content-Type:application/json``
-* SAPM at ``/v2/trace/sapm`` with ``Content-Type:application/x-protobuf``
 
 For more information on the ingest API endpoints, see :new-page:`Send APM traces <https://dev.splunk.com/observability/docs/apm/send_traces/>`. 
 

gdi/opentelemetry/components/sapm-receiver.rst

@@ -1,13 +1,11 @@
 .. _sapm-receiver:
 
-****************************
-SAPM receiver
-****************************
+********************************************
+Splunk APM (SAPM) receiver (deprecated)
+********************************************
 
 .. meta::
       :description: Receives traces from other collectors or from the SignalFx Smart Agent.
 
-The Splunk Distribution of the OpenTelemetry Collector supports the SAPM receiver. Documentation is planned for a future release. 
-
-To find information about this component in the meantime, see :new-page:`SAPM receiver <https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/sapmreceiver>` on GitHub.
+.. caution:: The SAPM receiver is deprecated and will be removed in April 2025. To receive traces from other Collector instances use the :ref:`otlp-receiver` instead.
 

gdi/opentelemetry/components/signalfx-exporter.rst

@@ -1,7 +1,7 @@
 .. _signalfx-exporter:
 
 *************************
-SignalFx exporter
+SignalFx exporter 
 *************************
 
 .. meta::

gdi/opentelemetry/components/splunk-apm-exporter.rst

@@ -1,22 +1,19 @@
 .. _splunk-apm-exporter:
 
-Splunk APM exporter
-**************************
+****************************************************
+Splunk APM (SAPM) exporter (deprecated)
+****************************************************
 
 .. meta::
       :description: Use the Splunk APM (SAPM) exporter to send traces from multiple nodes or services in a single batch. Read on to learn how to configure the component.
 
+.. caution:: The SAPM exporter is deprecated and will be removed in April 2025. To send traces to Splunk Observability Cloud use the :ref:`otlp-exporter` instead.
+
 The Splunk APM (SAPM) exporter allows the OpenTelemetry Collector to send traces to Splunk Observability Cloud. The supported pipeline types are ``traces``. See :ref:`otel-data-processing` for more information.
 
 Get started
 ======================
 
-.. note:: 
-  
-  This component is included in the default configuration of the Splunk Distribution of the OpenTelemetry Collector when deploying in host monitoring (agent) mode in the ``traces`` pipeline. See :ref:`otel-deployment-mode` for more information. 
-  
-  For details about the default configuration, see :ref:`otel-kubernetes-config`, :ref:`linux-config-ootb`, or :ref:`windows-config-ootb`. You can customize your configuration any time as explained in this document.
-
 Follow these steps to configure and activate the component:
 
 1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform: