Sweep configs

Author: aurbiztondo-splunk

gdi/get-data-in/application/otel-dotnet/sfx/troubleshooting/common-dotnet-troubleshooting.rst

@@ -69,9 +69,9 @@ Traces don't appear in Splunk Observability Cloud
 If traces from your instrumented application or service are not available in Splunk Observability Cloud, verify the OpenTelemetry Collector configuration:
 
 * Make sure that the Splunk Distribution of OpenTelemetry Collector is running.
-* Make sure that a ``zipkin`` receiver and a ``sapm`` exporter are configured.
+* Make sure that a ``zipkin`` receiver and an ``otlp`` exporter are configured.
 * Make sure that the ``access_token`` and ``endpoint`` fields are configured.
-* Check that the traces pipeline is configured to use the ``zipkin`` receiver and ``sapm`` exporter.
+* Check that the traces pipeline is configured to use the ``zipkin`` receiver and ``otlp`` exporter.
 
 Metrics don't appear in Splunk Observability Cloud
 ==================================================================

gdi/opentelemetry/components/attributes-processor.rst

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

gdi/opentelemetry/components/logging-exporter.rst

@@ -45,7 +45,7 @@ To activate the logging exporter, add it to any pipeline you want to diagnose. F
          - memory_limiter
          - batch
          - resourcedetection
-         exporters: [sapm, signalfx, logging]
+         exporters: [otlphttp, signalfx, logging]
        metrics:
          receivers: [hostmetrics, otlp, signalfx]
          processors: [memory_limiter, batch, resourcedetection]

gdi/opentelemetry/components/transform-processor.rst

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

gdi/opentelemetry/deployment-modes.rst

@@ -263,9 +263,9 @@ To set the Collector in data forwarding (gateway) mode to receiving data from an
 
    exporters:
       # Traces (Agent)
-      sapm:
+      otlphttp:
          access_token: "${SPLUNK_ACCESS_TOKEN}"
-         endpoint: "https://ingest.${SPLUNK_REALM}.signalfx.com/v2/trace"
+         endpoint: "https://ingest.${SPLUNK_REALM}.signalfx.com/v2/trace/otlp"
       # Metrics + Events (Agent)
       signalfx:
          access_token: "${SPLUNK_ACCESS_TOKEN}"
@@ -285,7 +285,7 @@ To set the Collector in data forwarding (gateway) mode to receiving data from an
             processors:
             - memory_limiter
             - batch
-            exporters: [sapm]
+            exporters: [otlphttp]
          metrics:
             receivers: [otlp]
             processors: [memory_limiter, batch]
@@ -317,9 +317,9 @@ If you want to use the :ref:`signalfx-exporter` for metrics on both agent and ga
 
    exporters:
       # Traces
-      sapm:
+      otlphttp:
          access_token: "${SPLUNK_ACCESS_TOKEN}"
-         endpoint: "https://ingest.${SPLUNK_REALM}.signalfx.com/v2/trace"
+         traces_endpoint: "https://ingest.${SPLUNK_REALM}.signalfx.com/v2/trace/otlp"
       # Metrics + Events (Agent)
       signalfx:
          access_token: "${SPLUNK_ACCESS_TOKEN}"
@@ -340,7 +340,7 @@ If you want to use the :ref:`signalfx-exporter` for metrics on both agent and ga
             processors:
             - memory_limiter
             - batch
-            exporters: [sapm]
+            exporters: [otlphttp]
          metrics:
             receivers: [signalfx]
             processors: [memory_limiter, batch]

gdi/opentelemetry/exposed-endpoints.rst

@@ -32,8 +32,6 @@ See the table for a complete list of exposed ports and endpoints:
     - OTLP receiver using gRPC and http
   * - ``http(s)://0.0.0.0:6060``
     - HTTP forwarder used to receive Smart Agent ``apiUrl`` data
-  * - ``http(s)://0.0.0.0:7276``
-    - SAPM trace receiver
   * - ``http://localhost:8888/metrics``
     - :new-page:`Internal Prometheus metrics <https://opentelemetry.io/docs/collector/internal-telemetry>` 
   * - ``http(s)://localhost:8006``

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

@@ -36,7 +36,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 an OTLP exporter and a SignalFx exporter as each pipeline's exporter, respectively. See more on :ref:`exporters <collector-components-processors>`.
 
 Configure the Smart Agent receiver 
 ------------------------------------------------------------
@@ -106,9 +106,9 @@ Configuration example
       signalfx:
          access_token: "${SIGNALFX_ACCESS_TOKEN}"
          realm: us1
-      sapm:
+      otlphttp:
          access_token: "${SIGNALFX_ACCESS_TOKEN}"
-         endpoint: https://ingest.us1.signalfx.com/v2/trace
+         traces_endpoint: https://ingest.us1.signalfx.com/v2/trace/otlp
 
    service:
       pipelines:
@@ -134,6 +134,6 @@ Configuration example
             processors:
                - resourcedetection
             exporters:
-               - sapm
+               - otlphttp
 
 

metrics-and-metadata/relatedcontent-collector-apm.rst

@@ -96,7 +96,7 @@ Here are the relevant config snippets from each section:
 
   exporters:
     # Traces
-    sapm:
+    otlphttp:
       access_token: "${SPLUNK_ACCESS_TOKEN}"
       endpoint: "${SPLUNK_TRACE_URL}"
     # Metrics + Events + APM correlation calls
@@ -113,7 +113,7 @@ Here are the relevant config snippets from each section:
       traces:
         receivers: [jaeger, zipkin]
         processors: [memory_limiter, batch, resourcedetection, resource/add_environment]
-        exporters: [sapm, signalfx]
+        exporters: [otlphttp, signalfx]
       metrics:
         receivers: [hostmetrics]
         processors: [memory_limiter, batch, resourcedetection]
@@ -257,9 +257,9 @@ Here are the relevant config snippets from each section:
 
   exporters:
     # Traces
-    sapm:
+    otlphttp:
       access_token: "${SPLUNK_ACCESS_TOKEN}"
-      endpoint: "https://ingest.${SPLUNK_REALM}.signalfx.com/v2/trace"
+      traces_endpoint: "https://ingest.${SPLUNK_REALM}.signalfx.com/v2/trace/otlp"
     # Metrics + Events
     signalfx:
       access_token: "${SPLUNK_ACCESS_TOKEN}"
@@ -273,7 +273,7 @@ Here are the relevant config snippets from each section:
         processors:
         - memory_limiter
         - batch
-        exporters: [sapm]
+        exporters: [otlphttp]
       metrics:
         receivers: [otlp]
         processors: [memory_limiter, batch]
@@ -293,9 +293,9 @@ Configure the agent in gateway mode as follows:
 
   exporters:
     # Traces
-    sapm:
+    otlphttp:
       access_token: "${SPLUNK_ACCESS_TOKEN}"
-      endpoint: "https://ingest.${SPLUNK_REALM}.signalfx.com/v2/trace"
+      endpoint: "https://ingest.${SPLUNK_REALM}.signalfx.com/v2/trace/otlp"
     # Metrics + Events
     signalfx:
       access_token: "${SPLUNK_ACCESS_TOKEN}"
@@ -311,7 +311,7 @@ Configure the agent in gateway mode as follows:
         processors:
         - memory_limiter
         - batch
-        exporters: [sapm]
+        exporters: [otlphttp]
       metrics:
         receivers: [signalfx]
         processors: [memory_limiter, batch]