Minimal tracing mode

content/en/docs/refguide/runtime/custom-settings/_index.md

@@ -101,7 +101,7 @@ There are two main ways that you might use to host multiple applications.
 * Routing based on a (sub)domain
 * Routing based on a subpath
 
-Say we are hosting two apps, App1 and App2. In domain-based routing, every app gets its own domain (for example. `app1.domain.com` and `app2.domain.com`). In subpath-based routing, this would be on a subpath, for example `domain.com/app1` and `domain.com/app2`.
+Say we are hosting two apps: App1 and App2. In domain-based routing, every app gets its own domain (for example. `app1.domain.com` and `app2.domain.com`). In subpath-based routing, this would be on a subpath, for example `domain.com/app1` and `domain.com/app2`.
 
 When setting up either routing variant, most content is correctly served automatically as it is relative to the path in which it is being served. Exceptions to this include:
 
@@ -170,7 +170,7 @@ These settings are configured *per runtime instance*. If you have [scaled your a
 
 ### Migration Settings
 
-The settings below are used to define the source database from which all data should be copied to the main database. You have to specify the settings below only once. The main database should exist and should be empty. During the app start-up, the data will be copied if the settings below are specified. Remove the settings afterwards, because they are not needed anymore.
+The settings below are used to define the source database from which all data should be copied to the main database. You have to specify the settings below only once. The main database should exist and should be empty. During the app start-up, the data will be copied if the settings below are specified. Remove the settings afterward, because they are not needed anymore.
 
 Before the data copying process starts, the main database structure will be generated based on the source database structure. This is necessary to make sure all the data is copied without any problems, especially in cases where the source database has a larger element value than the current domain model specifies.
 
@@ -305,6 +305,14 @@ The settings below configure metrics through [micrometer](https://micrometer.io/
 | <a id="MetricsRegistries" href="#MetricsRegistries">Metrics.Registries</a> | Registries to send metrics to | |
 | <a id="MetricsApplicationTags" href="#MetricsApplicationTags">Metrics.ApplicationTags</a> | Common tags used for every meter | |
 
+## OpenTelemetry Settings{#tracing-settings}
+
+The setting below configures observability (metrics, tracing, logs) through [OpenTelemetry](https://opentelemetry.io/docs). See [OpenTelemetry](/refguide/opentelemetry-in-runtime/) for information on setting up OpenTelemetry.
+
+| Name | Description | Default Value |
+| --- | --- | --- |
+| <a id="OpenTelemetryMinimalMode" href="#OpenTelemetryMinimalMode">OpenTelemetry.MinimalMode</a> | Enable OpenTelemetry minimal tracing mode. <br />When true, only generates incoming or outgoing spans. <br />*Introduced in Mendix version 11.15.0* | false |
+
 ## Proxy Settings {#proxy-settings}
 
 ### Http(s) Connections
@@ -350,7 +358,7 @@ These settings have to be set as JVM properties, not as custom runtime settings.
 The `https.` part of the names of these settings does not imply anything about whether the `HTTP` or `HTTPS` protocol is used - it is just the name of the setting.
 {{% /alert %}}
 
-### Non-proxy hosts {#non-proxy-hosts}
+### Non-Proxy Hosts {#non-proxy-hosts}
 
 {{% alert color="info" %}}
 Using `http.nonProxyHosts` for http(s) connections was introduced in Mendix 11.10.0.

content/en/docs/refguide/runtime/tracing-in-runtime.md

@@ -67,6 +67,18 @@ You can filter out specific traces using the `mendix.tracing.filter` system prop
 ]
 ```
 
+### Minimal Tracing Mode {#minimal-tracing-mode}
+
+{{% alert color="info" %}}
+Minimal tracing mode was introduced in Mendix 11.15.0.
+{{% /alert %}}
+
+In a multi-app landscape, you might want to track how requests flow between applications rather than examining the detailed handling within a single app. Tracing can also generate an overwhelming number of spans.
+
+Minimal tracing mode helps reduce the number of spans by recording only incoming and outgoing spans.
+
+To enable minimal tracing mode, set the `OpenTelemetry.MinimalMode` [custom runtime setting](/refguide/custom-settings/#OpenTelemetryMinimalMode) to `true`.
+
 ### Testing
 
 You can test the tracing using [Jaeger](https://www.jaegertracing.io/) or [Grafana](https://grafana.com).
@@ -85,7 +97,7 @@ Alternatively, you can set up the [OpenTelemetry collector](https://opentelemetr
 
 The following settings are supported by the Mendix runtime. See [Configure the SDK](https://opentelemetry.io/docs/languages/java/configuration/#environment-variables-and-system-properties) for more information about the settings that are prefixed with `otel.`.
 
-You can configure the Java Agent through system properties which can be added to the **Extra JVM parameters** field (for example, `-Dotel.exporter.otlp.traces.endpoint`), or set through environment variables. 
+You can configure the Java Agent through system properties which can be added to the **Extra JVM parameters** field (for example, `-Dotel.exporter.otlp.traces.endpoint`), or set through environment variables.
 
 | Name | Description | Default |
 | ---- | ----------- | ------- |
@@ -145,9 +157,9 @@ Replace `MyServiceName` with a meaningful identifier for your service, and `coll
 
 ## Sending Traces to Datadog
 
-You can export OpenTelemetry traces to Datadog using one of the following two ways: 
+You can export OpenTelemetry traces to Datadog using one of the following two ways:
 
-* Datadog Distribution of OpenTelemetry (DDOT) 
+* Datadog Distribution of OpenTelemetry (DDOT)
 * OpenTelemetry Collector
 
 ### Datadog Distribution of OpenTelemetry (DDOT)
@@ -158,12 +170,12 @@ For installation instructions, refer to the official [DDOT documentation](https:
 
 ### OpenTelemetry Collector
 
-You can install the OpenTelemetry Collector on various operating systems, including Windows, macOS, and Linux. 
+You can install the OpenTelemetry Collector on various operating systems, including Windows, macOS, and Linux.
 
-To use the OpenTelemetry Collector with Datadog, follow these steps:  
+To use the OpenTelemetry Collector with Datadog, follow these steps:
 
 1. Install the OpenTelemetry Collector by following the official [installation guide](https://opentelemetry.io/docs/collector/installation/).
-2. Install the `otelcol_contrib` package instead of `otelcol` to include Datadog support. 
+2. Install the `otelcol_contrib` package instead of `otelcol` to include Datadog support.
 3. Run the collector with the [appropriate configuration](https://docs.datadoghq.com/opentelemetry/setup/collector_exporter/install/#2---configure-the-datadog-exporter-and-connector) adapted for Datadog.
 
 ## Sending Traces from Mendix on Kubernetes