From c065b1934ba2b45737a4b2e26eb957c155747702 Mon Sep 17 00:00:00 2001 From: Leroy van Engelen <223281140+lvanengelen-mx@users.noreply.github.com> Date: Mon, 21 Sep 2026 14:04:00 +0200 Subject: [PATCH 1/6] Document OpenTelemetry.MinimalMode custom runtime setting --- .../en/docs/refguide/runtime/custom-settings/_index.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/en/docs/refguide/runtime/custom-settings/_index.md b/content/en/docs/refguide/runtime/custom-settings/_index.md index ba63320b192..fd2f8d3296e 100644 --- a/content/en/docs/refguide/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide/runtime/custom-settings/_index.md @@ -305,6 +305,14 @@ The settings below configure metrics through [micrometer](https://micrometer.io/ | Metrics.Registries | Registries to send metrics to | | | Metrics.ApplicationTags | Common tags used for every meter | | +## OpenTelemetry Settings{#tracing-settings} + +The settings below configure observability (metrics, tracing, logs) through [OpenTelemetry](https://opentelemetry.io/docs). See [OpenTelemetry](/refguide/opentelemetry-in-runtime/) for more information on OpenTelemetry setup. + +| Name | Description | Default Value | +| --- | --- | --- | +| OpenTelemetry.MinimalMode | Enable OpenTelemetry minimal tracing mode. Only generate ingoing or outgoing spans. | false | + ## Proxy Settings {#proxy-settings} ### Http(s) Connections From 3dd717563c740ef29e2a319cbdbdadb192a5865a Mon Sep 17 00:00:00 2001 From: Leroy van Engelen <223281140+lvanengelen-mx@users.noreply.github.com> Date: Mon, 21 Sep 2026 14:04:00 +0200 Subject: [PATCH 2/6] Remove EOL-spaces --- .../en/docs/refguide/runtime/tracing-in-runtime.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/refguide/runtime/tracing-in-runtime.md b/content/en/docs/refguide/runtime/tracing-in-runtime.md index 247a5c376aa..1c1b72300d7 100644 --- a/content/en/docs/refguide/runtime/tracing-in-runtime.md +++ b/content/en/docs/refguide/runtime/tracing-in-runtime.md @@ -85,7 +85,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 +145,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 +158,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 From 5eea02cf85aeae9291d9c6ecfabd5cbcda2105d2 Mon Sep 17 00:00:00 2001 From: Leroy van Engelen <223281140+lvanengelen-mx@users.noreply.github.com> Date: Mon, 21 Sep 2026 14:04:00 +0200 Subject: [PATCH 3/6] Document minimal tracing mode --- content/en/docs/refguide/runtime/tracing-in-runtime.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/content/en/docs/refguide/runtime/tracing-in-runtime.md b/content/en/docs/refguide/runtime/tracing-in-runtime.md index 1c1b72300d7..197de509c56 100644 --- a/content/en/docs/refguide/runtime/tracing-in-runtime.md +++ b/content/en/docs/refguide/runtime/tracing-in-runtime.md @@ -67,6 +67,15 @@ 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 by recording only ingoing and outgoing spans. + +Enable minimal tracing mode by setting the `OpenTelemetry.MinimalMode` [custom runtime setting](/refguide/custom-settings) to `true`. ### Testing You can test the tracing using [Jaeger](https://www.jaegertracing.io/) or [Grafana](https://grafana.com). From 04687f6dfff3aaa39b2308d2378627dabc9711e3 Mon Sep 17 00:00:00 2001 From: Leroy van Engelen <223281140+lvanengelen-mx@users.noreply.github.com> Date: Mon, 21 Sep 2026 15:11:46 +0200 Subject: [PATCH 4/6] Review: fix embarrassing language mistake --- content/en/docs/refguide/runtime/custom-settings/_index.md | 2 +- content/en/docs/refguide/runtime/tracing-in-runtime.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide/runtime/custom-settings/_index.md b/content/en/docs/refguide/runtime/custom-settings/_index.md index fd2f8d3296e..5020d89c3a4 100644 --- a/content/en/docs/refguide/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide/runtime/custom-settings/_index.md @@ -311,7 +311,7 @@ The settings below configure observability (metrics, tracing, logs) through [Ope | Name | Description | Default Value | | --- | --- | --- | -| OpenTelemetry.MinimalMode | Enable OpenTelemetry minimal tracing mode. Only generate ingoing or outgoing spans. | false | +| OpenTelemetry.MinimalMode | Enable OpenTelemetry minimal tracing mode. Only generate incoming or outgoing spans. | false | ## Proxy Settings {#proxy-settings} diff --git a/content/en/docs/refguide/runtime/tracing-in-runtime.md b/content/en/docs/refguide/runtime/tracing-in-runtime.md index 197de509c56..82f6a66eb4d 100644 --- a/content/en/docs/refguide/runtime/tracing-in-runtime.md +++ b/content/en/docs/refguide/runtime/tracing-in-runtime.md @@ -73,7 +73,7 @@ You can filter out specific traces using the `mendix.tracing.filter` system prop 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 by recording only ingoing and outgoing spans. +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 by recording only incoming and outgoing spans. Enable minimal tracing mode by setting the `OpenTelemetry.MinimalMode` [custom runtime setting](/refguide/custom-settings) to `true`. ### Testing From 327df62440a3178c1c2146b798a6206726187073 Mon Sep 17 00:00:00 2001 From: MarkvanMents Date: Tue, 29 Sep 2026 15:13:16 +0200 Subject: [PATCH 5/6] Proofread --- .../en/docs/refguide/runtime/custom-settings/_index.md | 10 +++++----- content/en/docs/refguide/runtime/tracing-in-runtime.md | 7 +++++-- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/content/en/docs/refguide/runtime/custom-settings/_index.md b/content/en/docs/refguide/runtime/custom-settings/_index.md index 5020d89c3a4..87bafda93e3 100644 --- a/content/en/docs/refguide/runtime/custom-settings/_index.md +++ b/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. @@ -307,11 +307,11 @@ The settings below configure metrics through [micrometer](https://micrometer.io/ ## OpenTelemetry Settings{#tracing-settings} -The settings below configure observability (metrics, tracing, logs) through [OpenTelemetry](https://opentelemetry.io/docs). See [OpenTelemetry](/refguide/opentelemetry-in-runtime/) for more information on OpenTelemetry setup. +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 | | --- | --- | --- | -| OpenTelemetry.MinimalMode | Enable OpenTelemetry minimal tracing mode. Only generate incoming or outgoing spans. | false | +| OpenTelemetry.MinimalMode | Enable OpenTelemetry minimal tracing mode.
When true, only generates incoming or outgoing spans.
*Introduced in Mendix version 11.15.0* | false | ## Proxy Settings {#proxy-settings} @@ -358,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. diff --git a/content/en/docs/refguide/runtime/tracing-in-runtime.md b/content/en/docs/refguide/runtime/tracing-in-runtime.md index 82f6a66eb4d..83a6bde158d 100644 --- a/content/en/docs/refguide/runtime/tracing-in-runtime.md +++ b/content/en/docs/refguide/runtime/tracing-in-runtime.md @@ -73,9 +73,12 @@ You can filter out specific traces using the `mendix.tracing.filter` system prop 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 by recording only incoming and outgoing spans. +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`. -Enable minimal tracing mode by setting the `OpenTelemetry.MinimalMode` [custom runtime setting](/refguide/custom-settings) to `true`. ### Testing You can test the tracing using [Jaeger](https://www.jaegertracing.io/) or [Grafana](https://grafana.com). From 980e8e67fab98831efcbdbd8c20da940d7758256 Mon Sep 17 00:00:00 2001 From: MarkvanMents Date: Tue, 29 Sep 2026 15:15:11 +0200 Subject: [PATCH 6/6] Typo --- content/en/docs/refguide/runtime/custom-settings/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/refguide/runtime/custom-settings/_index.md b/content/en/docs/refguide/runtime/custom-settings/_index.md index 87bafda93e3..3f5384f2fe5 100644 --- a/content/en/docs/refguide/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide/runtime/custom-settings/_index.md @@ -358,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.