Merge pull request #2640 from splunk/urbiz-DG27923-endpoint

[DG27923]: Remove deprecated splunk.metrics.endpoint

Author: aurbiztondo-splunk

apm/profiling/get-data-in-profiling.rst

@@ -139,7 +139,6 @@ To activate AlwaysOn Profiling, follow the steps for the appropriate programming
          -Dsplunk.profiler.enabled=true \
          -Dsplunk.profiler.memory.enabled=true \
          -Dotel.exporter.otlp.endpoint=http(s)://collector:4317 \
-         -Dsplunk.metrics.endpoint=http(s)://collector:9943
          -jar <your_application>.jar
 
       For more configuration options, including setting a separate endpoint for profiling data, see :ref:`profiling-configuration-java`.

gdi/get-data-in/application/java/instrumentation/instrument-java-application.rst

@@ -144,7 +144,6 @@ The following example shows how to activate the profiler using the system proper
    -Dsplunk.profiler.enabled=true \
    -Dsplunk.profiler.memory.enabled=true \
    -Dotel.exporter.otlp.endpoint=http(s)://collector:4318 \
-   -Dsplunk.metrics.endpoint=http(s)://collector:4318
    -jar <your_application>.jar
 
 See :ref:`get-data-in-profiling` for more information. For more settings, see :ref:`profiling-configuration-java`.

gdi/get-data-in/application/java/migrate-metrics.rst

@@ -98,7 +98,7 @@ To migrate your instrumentation to the version 2.5.0 or higher of the Java agent
    - Select :guilabel:`Data Migration`.
    - Inside the :guilabel:`Start migration` card, select :guilabel:`Start`.
 
-2. Turn on OTLP histograms in the Splunk Distribution of OpenTelemetry Collector.
+2. Turn on OTLP histograms in the Splunk Distribution of the OpenTelemetry Collector.
 
 
 

gdi/get-data-in/application/java/troubleshooting/common-java-troubleshooting.rst

@@ -164,17 +164,21 @@ Make sure that you're using a valid Splunk access token when sending data direct
 Metrics exporter issues
 ===============================================================
 
-If you see warnings about metrics in your logs, it might mean that the Java agent can't send metrics to your OTel Collector, Smart Agent (now deprecated), or to the Splunk platform endpoints:
+.. note:: See also :ref:`java-metrics-migration-guide`.
+
+If you see warnings about metrics in your logs, it might mean that the Java agent can't send metrics to your OTel Collector instance or to the Splunk platform endpoints:
 
 To troubleshoot connectivity issues affecting application metrics, try the following steps:
 
-1. Make sure that ``splunk.metrics.endpoint`` points to the correct host.
+1. Make sure that you've removed the deprecated property ``splunk.metrics.endpoint`` from your configuration.
+
+2. Check that the OpenTelemetry Collector is configured and running.
 
-2. Check that the OpenTelemetry Collector or Smart Agent instance is configured and running.
+  * If you're using the :ref:`otlp-receiver`, make sure it points to the correct host/endpoint, for example ``http://<host>:4318/v1/metrics``.
 
-3. Check that the OpenTelemetry Collector or Smart Agent are using the correct ports for the SignalFx receiver. The Collector uses ``http://<host>:4318/v2/datapoint``, and the Smart Agent uses ``http://<host>:9080/v2/datapoint``.
+  * If you're using the :ref:`signalfx-receiver`, make sure it points to ``http://<host>:4318/v2/datapoint``.
 
-4. Make sure that you're using a valid Splunk access token when sending data directly to your Splunk platform instance. See :ref:`admin-api-access-tokens`.
+3. Make sure that you're using a valid Splunk access token when sending data directly to your Splunk platform instance. See :ref:`admin-api-access-tokens`.
 
 
 .. _java-profiler-issues:

gdi/opentelemetry/components/signalfx-receiver.rst

@@ -9,7 +9,7 @@ SignalFx receiver
 
 The SignalFx receiver is a native OpenTelemetry component that allows the Splunk Distribution of the OpenTelemetry Collector to collect data in SignalFx proto format. Supported pipeline types are ``metrics`` and ``logs``. See :ref:`otel-data-processing` for more information.
 
-.. note:: While the SignalFx Smart Agent has reached End of Support, OTel native components such as the Smart Agent receiver, the SignalFx receiver, and the SignalFx exporter are available and supported. For information on the exporter, see :ref:`signalfx-exporter`.
+.. note:: For information on the SignalFx exporter, see :ref:`signalfx-exporter`.
 
 The SignalFx receiver accepts: