From 3e81dfb8bd06c0b00c8d11871a276de287ab2528 Mon Sep 17 00:00:00 2001 From: jason plumb <75337021+breedx-splk@users.noreply.github.com> Date: Fri, 11 Apr 2025 09:10:09 -0700 Subject: [PATCH 1/3] Fix metrics endpoint path --- gdi/opentelemetry/components/otlphttp-exporter.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gdi/opentelemetry/components/otlphttp-exporter.rst b/gdi/opentelemetry/components/otlphttp-exporter.rst index bb0a262c0..52fa2cdbe 100644 --- a/gdi/opentelemetry/components/otlphttp-exporter.rst +++ b/gdi/opentelemetry/components/otlphttp-exporter.rst @@ -46,7 +46,7 @@ The following settings are optional and can be added to the configuration for mo * ``logs_endpoint``. The target URL to send log data to. For example, ``https://example.com:4318/v1/logs``. -* ``metrics_endpoint``. The target URL to send metric data to. For example, ``"https://ingest.us0.signalfx.com/v2/trace/otlp"`` to send metrics to Splunk Observability Cloud. +* ``metrics_endpoint``. The target URL to send metric data to. For example, ``"https://ingest.us0.signalfx.com/v2/datapoint/otlp"`` to send metrics to Splunk Observability Cloud. * ``tls``. See :ref:`TLS Configuration Settings ` in this document for the full set of available options. Only applicable for sending data to a custom endpoint. From c406bc7920235c33e351002b24a782e13b634a70 Mon Sep 17 00:00:00 2001 From: jcatera-splunk Date: Fri, 11 Apr 2025 09:43:57 -0700 Subject: [PATCH 2/3] Update otlphttp-exporter.rst Adding the `metrics_endpoint` to the sample configuration as the example only defined one endpoint, and the endpoints are different. --- gdi/opentelemetry/components/otlphttp-exporter.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/gdi/opentelemetry/components/otlphttp-exporter.rst b/gdi/opentelemetry/components/otlphttp-exporter.rst index 52fa2cdbe..d4f7b2113 100644 --- a/gdi/opentelemetry/components/otlphttp-exporter.rst +++ b/gdi/opentelemetry/components/otlphttp-exporter.rst @@ -67,6 +67,7 @@ To send traces and metrics to Splunk Observability Cloud using OTLP over HTTP, c otlphttp: # The target URL to send trace data to. By default it's set to ``https://ingest.${SPLUNK_REALM}.signalfx.com/v2/trace/otlp``. traces_endpoint: https://ingest..signalfx.com/v2/trace/otlp + metrics_endpoint: https://ingest.us0.signalfx.com/v2/datapoint/otlp # Set of HTTP headers added to every request. headers: # X-SF-Token is the authentication token provided by Splunk Observability Cloud. From e91d2d86d82329e001c70145509b0726982b491f Mon Sep 17 00:00:00 2001 From: jcatera-splunk Date: Fri, 11 Apr 2025 09:58:44 -0700 Subject: [PATCH 3/3] Update otlphttp-exporter.rst Replaced the domain values with the placeholder . --- gdi/opentelemetry/components/otlphttp-exporter.rst | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/gdi/opentelemetry/components/otlphttp-exporter.rst b/gdi/opentelemetry/components/otlphttp-exporter.rst index d4f7b2113..ee5595810 100644 --- a/gdi/opentelemetry/components/otlphttp-exporter.rst +++ b/gdi/opentelemetry/components/otlphttp-exporter.rst @@ -46,7 +46,7 @@ The following settings are optional and can be added to the configuration for mo * ``logs_endpoint``. The target URL to send log data to. For example, ``https://example.com:4318/v1/logs``. -* ``metrics_endpoint``. The target URL to send metric data to. For example, ``"https://ingest.us0.signalfx.com/v2/datapoint/otlp"`` to send metrics to Splunk Observability Cloud. +* ``metrics_endpoint``. The target URL to send metric data to. For example, ``"https://ingest..signalfx.com/v2/datapoint/otlp"`` to send metrics to Splunk Observability Cloud. * ``tls``. See :ref:`TLS Configuration Settings ` in this document for the full set of available options. Only applicable for sending data to a custom endpoint. @@ -67,7 +67,8 @@ To send traces and metrics to Splunk Observability Cloud using OTLP over HTTP, c otlphttp: # The target URL to send trace data to. By default it's set to ``https://ingest.${SPLUNK_REALM}.signalfx.com/v2/trace/otlp``. traces_endpoint: https://ingest..signalfx.com/v2/trace/otlp - metrics_endpoint: https://ingest.us0.signalfx.com/v2/datapoint/otlp + # The target URL to send metrics data to. By default it's set to ``https://ingest.${SPLUNK_REALM}.signalfx.com/v2/datapoint/otlp``. + metrics_endpoint: https://ingest..signalfx.com/v2/datapoint/otlp # Set of HTTP headers added to every request. headers: # X-SF-Token is the authentication token provided by Splunk Observability Cloud. @@ -93,8 +94,8 @@ This is a detailed configuration example: .. code-block:: yaml endpoint: "https://1.2.3.4:1234" - traces_endpoint: https://ingest.us0.signalfx.com/v2/trace/otlp - metrics_endpoint: https://ingest.us0.signalfx.com/v2/datapoint/otlp + traces_endpoint: https://ingest..signalfx.com/v2/trace/otlp + metrics_endpoint: https://ingest..signalfx.com/v2/datapoint/otlp headers: X-SF-Token: timeout: 10s @@ -161,8 +162,8 @@ For example: exporters: otlphttp: - metrics_endpoint: https://ingest.lab0.signalfx.com/v2/datapoint/otlp - traces_endpoint: https://ingest.lab0.signalfx.com/v2/trace/otlp + metrics_endpoint: https://ingest..signalfx.com/v2/datapoint/otlp + traces_endpoint: https://ingest..signalfx.com/v2/trace/otlp headers: "X-SF-Token": "mytoken" auth: