Update readme

Author: asreehari-splunk

.chloggen/deprecate_sapmexporter.yaml

@@ -21,9 +21,9 @@ subtext: |
   ```yaml
     exporters:
         otlphttp:
-            traces_endpoint: "${INGEST_URL}/v2/trace/otlp"
+            traces_endpoint: "${SPLUNK_INGEST_URL}/v2/trace/otlp"
             headers:
-                "X-SF-Token": "${ACCESS_TOKEN}"
+                "X-SF-Token": "${SPLUNK_ACCESS_TOKEN}"
     ```
 
 # If your change doesn't affect end users or the exported elements of any package,

exporter/sapmexporter/README.md

@@ -12,6 +12,21 @@
 [contrib]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib
 <!-- end autogenerated section -->
 
+### Deprecated
+> The SAPM protocol is based on the Jaeger protocol, which is no longer the preferred approach of the community, with the advent of the OTLP protocol. The Jaeger exporters have been removed from the collector already. Jaeger itself is migrating to use the OTel data format internally.
+
+> As a result, the SAPM exporter is being deprecated in favor of the OTLPHTTP exporter. The following configuration can be used for the OTLPHTTP exporter
+
+```yaml
+exporters:
+  otlphttp:
+    traces_endpoint: "${SPLUNK_INGEST_URL}/v2/trace/otlp"
+    headers:
+        "X-SF-Token": "${SPLUNK_ACCESS_TOKEN}"
+```
+
+
+
 The SAPM exporter builds on the Jaeger proto and adds additional batching on top. This allows
 the collector to export traces from multiples nodes/services in a single batch. The SAPM proto
 and some useful related utilities can be found [here](https://github.com/signalfx/sapm-proto/).