Merge pull request #2733 from splunk/repo-sync

Pulling refs/heads/main into main

Author: aurbiztondo-splunk

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.<realm>.signalfx.com/v2/datapoint/otlp"`` to send metrics to Splunk Observability Cloud.
 
 * ``tls``. See :ref:`TLS Configuration Settings <otlphttp-exporter-settings>` in this document for the full set of available options. Only applicable for sending data to a custom endpoint.
 
@@ -67,6 +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.<realm>.signalfx.com/v2/trace/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.<realm>.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.
@@ -92,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.<realm>.signalfx.com/v2/trace/otlp
+  metrics_endpoint: https://ingest.<realm>.signalfx.com/v2/datapoint/otlp
   headers:
     X-SF-Token: <access_token>
   timeout: 10s
@@ -160,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.<realm>.signalfx.com/v2/datapoint/otlp
+      traces_endpoint: https://ingest.<realm>.signalfx.com/v2/trace/otlp
       headers:
           "X-SF-Token": "mytoken"
       auth:

locales/ja_JA/LC_MESSAGES/_includes.mo

@@ -8,15 +8,15 @@ msgstr ""
 "Project-Id-Version: Splunk\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2025-01-29 18:45+0000\n"
-"PO-Revision-Date: 2025-02-27 12:02+0000\n"
+"PO-Revision-Date: 2025-04-09 18:56+0100\n"
 "Last-Translator: \n"
 "Language-Team: ja_JA <[email protected]>\n"
 "Language: ja_JA\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Generated-By: Babel 2.12.1\n"
-"X-Generator: Poedit 3.5\n"
+"X-Generator: Poedit 3.6\n"
 
 #: ../../analytics/infrastructure-monitoring-analytics.rst:-1
 msgid "Splunk infrastructure monitoring analytics overview, rollup policies, signalflow instructions, and analytics aggregations and transformations"
@@ -412,8 +412,8 @@ msgstr ""
 
 #: ../../analytics/signalflow.rst:138
 msgid ""
-"The timeshift feature in charts is aware of cycles having variable lengths, such as how March has more days than February, and shifts correctly to the end of a previous interval. By contrast, the standalone timeshift analytics function performs a fixed width shift, such as 30 days. For more information, see :ref:"
-"`use-timeshift-function-to-understand-trends`."
+"The timeshift feature in charts is aware of cycles having variable lengths, such as how March has more days than February, and shifts correctly to the end of a previous interval. By contrast, the standalone timeshift analytics function performs a fixed width shift, such as 30 days. For more information, "
+"see :ref:`use-timeshift-function-to-understand-trends`."
 msgstr "チャートのタイムシフト機能は、3月が2月より日数が多いというような、可変長のサイクルを認識し、前の間隔の終わりに正しくシフトします。対照的に、スタンドアローンのタイムシフト分析機能は、30日のような固定幅のシフトを行います。詳しくは :ref:`use-timeshift-function-to-understand-trends` を参照してください。"
 
 #: ../../analytics/signalflow.rst:143