From 339b6a1bca97454432223416d2cfdaf5901f4fbc Mon Sep 17 00:00:00 2001 From: D064278 Date: Thu, 17 Sep 2026 06:45:10 +0200 Subject: [PATCH 1/2] Add further clarification and align with wording in internal docs --- docs/configuration-parameters-1830bca.md | 6 ++++-- docs/ingest-via-opentelemetry-api-endpoint-fdc78af.md | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/configuration-parameters-1830bca.md b/docs/configuration-parameters-1830bca.md index f68f7af..31826bb 100644 --- a/docs/configuration-parameters-1830bca.md +++ b/docs/configuration-parameters-1830bca.md @@ -544,10 +544,12 @@ Boolean -When set to true, spans are written to OpenSearch individually as they arrive, without assembling complete traces. +When set to `true`, spans are written to OpenSearch individually as they arrive, without assembling complete traces. Defaults to `false`. + +This can be useful if you know that root/parent spans will be missing from your telemetry \(e.g., when only a subset of services in a request path emit spans\), so trace assembly cannot succeed anyway. In this case it lowers ingestion latency at the cost of trace completeness. > ### Note: -> When span\_passthrough is enabled, the service map \(otel-v1-apm-service-map index\) is not populated and trace views in OpenSearch Dashboards may show incomplete traces. Use this only when you need raw span data and do not require service map or full trace assembly. +> When `span_passthrough` is enabled, the `otel-v1-apm-service-map` index is not populated, so the Service Map view in the Observability plugin of OpenSearch Dashboards will not function and the Trace Analytics view may show orphaned spans rather than complete trace trees. diff --git a/docs/ingest-via-opentelemetry-api-endpoint-fdc78af.md b/docs/ingest-via-opentelemetry-api-endpoint-fdc78af.md index 5381d38..d75c0a3 100644 --- a/docs/ingest-via-opentelemetry-api-endpoint-fdc78af.md +++ b/docs/ingest-via-opentelemetry-api-endpoint-fdc78af.md @@ -41,7 +41,7 @@ OpenTelemetry support in SAP Cloud Logging needs to be enabled with a service in > } > ``` > - > When `span_passthrough` is set to `true`, spans are written to OpenSearch individually as they arrive. The service map is not populated and trace views may show incomplete traces. + > When `span_passthrough` is set to `true`, spans are written to OpenSearch individually as they arrive, without assembling complete traces. This can be useful if you know that root/parent spans will be missing from your telemetry \(e.g., when only a subset of services in a request path emit spans\), so trace assembly cannot succeed anyway. In this case it lowers ingestion latency at the cost of trace completeness. Furthermore, when enabled, the `otel-v1-apm-service-map` index is not populated, so the Service Map view in the Observability plugin of OpenSearch Dashboards will not function and the Trace Analytics view may show orphaned spans rather than complete trace trees. 2. Retrieve Endpoint and Certificates. From 61c2295869f1c866918bd88178554a4b320eac9b Mon Sep 17 00:00:00 2001 From: Nicklas Dohrn <20398358+nicklas-dohrn@users.noreply.github.com> Date: Wed, 23 Sep 2026 17:38:46 +0200 Subject: [PATCH 2/2] Update docs/ingest-via-opentelemetry-api-endpoint-fdc78af.md Co-authored-by: Jannik Brand --- .../ingest-via-opentelemetry-api-endpoint-fdc78af.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/ingest-via-opentelemetry-api-endpoint-fdc78af.md b/docs/ingest-via-opentelemetry-api-endpoint-fdc78af.md index d75c0a3..f4540ce 100644 --- a/docs/ingest-via-opentelemetry-api-endpoint-fdc78af.md +++ b/docs/ingest-via-opentelemetry-api-endpoint-fdc78af.md @@ -41,7 +41,17 @@ OpenTelemetry support in SAP Cloud Logging needs to be enabled with a service in > } > ``` > - > When `span_passthrough` is set to `true`, spans are written to OpenSearch individually as they arrive, without assembling complete traces. This can be useful if you know that root/parent spans will be missing from your telemetry \(e.g., when only a subset of services in a request path emit spans\), so trace assembly cannot succeed anyway. In this case it lowers ingestion latency at the cost of trace completeness. Furthermore, when enabled, the `otel-v1-apm-service-map` index is not populated, so the Service Map view in the Observability plugin of OpenSearch Dashboards will not function and the Trace Analytics view may show orphaned spans rather than complete trace trees. + > ### Note: + > If you only need raw span data and do not require service map or full trace assembly, you can enable span passthrough mode (see [ingest_otlp configuration parameter](configuration-parameters-1830bca.md#loio1830bca1b060484e9cfabc0e62472e8e__table_zcy_jjx_jzb)): + > + > ``` + > { + > "ingest_otlp": { + > "enabled": true, + > "span_passthrough": true + > } + > } + > ``` 2. Retrieve Endpoint and Certificates.