Sweep

Author: aurbiztondo-splunk

gdi/monitors-cloud/heroku.rst

@@ -9,7 +9,7 @@ Heroku
 The Splunk OpenTelemetry Connector for Heroku is a buildpack for the Splunk Distribution of the OpenTelemetry Collector. The buildpack installs
 and runs the Splunk OpenTelemetry Connector on a Dyno to receive, process and export metric and trace data for Splunk Observability Cloud:
 
--  Splunk APM through the ``sapm`` exporter. The ``otlphttp`` exporter can be used with a custom configuration.
+-  Splunk APM through the ``otlphttp`` exporter.
 -  Splunk Infrastructure Monitoring through the ``signalfx`` exporter.
 
 See :ref:`otel-intro` to learn more.

gdi/opentelemetry/components/filter-processor.rst

@@ -86,7 +86,7 @@ You can then add the filter processors to any compatible pipeline. For example:
          - memory_limiter
          - batch
          - resourcedetection
-         exporters: [sapm, signalfx]
+         exporters: [otlphttp, signalfx]
        metrics:
          receivers: [hostmetrics, otlp, signalfx]
          processors:

gdi/opentelemetry/components/groupbyattrs-processor.rst

@@ -70,7 +70,7 @@ Use the processor to perform the following actions:
 * :ref:`Compact multiple records <groupbyattrs-processor-compact>` that share the same ``resource`` and ``InstrumentationLibrary`` attributes but are under multiple ``ResourceSpans`` or ``ResourceMetrics`` or ``ResourceLogs`` into a single ``ResourceSpans`` or ``ResourceMetrics`` or ``ResourceLogs``, when an empty list of keys is provided. 
 
   * This happens, for example, when you use the ``groupbytrace`` processor, or when data comes in multiple requests. 
-  * If you compact data it takes less memory, it's more efficiently processed and serialized, and the number of export requests is reduced, for example if you use the ``sapm`` exporter. See more at :ref:`splunk-apm-exporter`.
+  * If you compact data it takes less memory, it's more efficiently processed and serialized, and the number of export requests is reduced.
 
 .. tip:: Use the ``groupbyattrs`` processor together with ``batch`` processor, as a consecutive step. Grouping records together under matching resource and/or InstrumentationLibrary reduces the fragmentation of data.
 

gdi/opentelemetry/components/jaeger-receiver.rst

@@ -94,7 +94,7 @@ The Jaeger receiver uses helper files for additional capabilities:
 Remote sampling
 -----------------------------------------------
 
-Since version 0.61.0, remote sampling is no longer supported. Instead, since version 0.59.0, use the ``jaegerremotesapmpling`` extension for remote sampling.
+Since version 0.61.0, remote sampling is no longer supported. Instead, since version 0.59.0, use the ``jaegerremotesampling`` extension for remote sampling.
 
 .. _jaeger-receiver-settings: