Draft: [RUN-5271] Rename tracing-in-runtime to opentelemetry-in-runtime

content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/datadog-metrics.md

@@ -208,7 +208,7 @@ If the app has more than one instance, you will see lines on the graph for each
 
 ## Mendix Tracing{#mendix-tracing}
 
-[Mendix Tracing](/refguide/tracing-in-runtime/) sends Mendix Runtime traces to [Datadog APM](https://docs.datadoghq.com/tracing/), giving you distributed tracing visibility into your app's performance and microflow executions.
+[Mendix Tracing](/refguide/opentelemetry-in-runtime/) sends Mendix Runtime traces to [Datadog APM](https://docs.datadoghq.com/tracing/), giving you distributed tracing visibility into your app's performance and microflow executions.
 
 {{% alert color="info" %}}
 Mendix Tracing requires Mendix Runtime 10.24.12 or above, or 11.5 or above.
@@ -232,7 +232,7 @@ To enable Mendix Tracing, follow these steps:
 
 ### Filtering Traces{#filter-traces}
 
-To control which traces are sent to Datadog, set the `MX_TRACING_FILTER` custom environment variable. For available filter options and syntax, see [Tracing in Runtime](/refguide/tracing-in-runtime/#filtering).
+To control which traces are sent to Datadog, set the `MX_TRACING_FILTER` custom environment variable. For available filter options and syntax, see [Tracing in Runtime](/refguide/opentelemetry-in-runtime/#filtering).
 
 ## Additional Information{#additional-info}
 
@@ -305,7 +305,7 @@ Previously, when Mendix Cloud ran on Cloud Foundry, hosts were incorrectly regis
 
 * [Monitor Your Mendix Apps with Datadog](https://www.mendix.com/blog/monitor-your-mendix-apps-with-datadog/) – a Mendix blog about the capabilities of Datadog and using Datadog with Mendix
 * [Metrics](/developerportal/operate/metrics/)
-* [Tracing in Runtime](/refguide/tracing-in-runtime/) – Mendix documentation
+* [Tracing in Runtime](/refguide/opentelemetry-in-runtime/) – Mendix documentation
 * [Java Runtime Metrics](https://docs.datadoghq.com/tracing/runtime_metrics/java/) – Datadog documentation
 * [Postgres](https://docs.datadoghq.com/integrations/postgres/) – Datadog documentation
 * [System Check](https://docs.datadoghq.com/integrations/system/) – Datadog documentation

content/en/docs/refguide/modeling/app-explorer/app/app-settings/configurations-tab.md

@@ -33,7 +33,7 @@ A configuration contains the following:
 * [Constants](#constants)
 * [Custom](#custom)
 * [Headers](#headers)
-* [OpenTelemetry](/refguide/tracing-in-runtime/#min-configuration)
+* [OpenTelemetry](/refguide/opentelemetry-in-runtime/#min-configuration)
 
 ### Database {#database}
 

content/en/docs/refguide/runtime/monitoring-mendix-runtime.md

@@ -674,7 +674,7 @@ This will write logs to standard output in simple text format.
 }
 ```
 
-This will send logs to the registered OpenTelemetry collector. See [Tracing](/refguide/tracing-in-runtime/) for a guide on how to enable OpenTelemetry.
+This will send logs to the registered OpenTelemetry collector. See [Tracing](/refguide/opentelemetry-in-runtime/) for a guide on how to enable OpenTelemetry.
 
 ## Set Log Levels{#log-levels}
 

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

@@ -1,7 +1,7 @@
 ---
-title: "Tracing"
-url: /refguide/tracing-in-runtime/
-description: "Describes how to setup and use tracing in the Mendix Runtime."
+title: "OpenTelemetry"
+url: /refguide/opentelemetry-in-runtime/
+description: "Describes how to setup and use OpenTelemetry in the Mendix Runtime."
 ---
 
 ## Introduction

content/en/docs/refguide/testing/_index.md

@@ -80,4 +80,4 @@ Performance testing involves unit-level performance checks for critical microflo
 
 You can use the following offerings to help with this test type:
 
-* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).
+* [Tracing](/refguide/opentelemetry-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).

content/en/docs/releasenotes/studio-pro/11/11.0.md

@@ -66,9 +66,9 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro
 * We added support for Brazilian Portuguese to Studio Pro.
 * We improved the messages that Studio Pro shows when running an OQL query in view entities. There are now clearer messages when the app has not fully started yet and when the query refers to `[%CurrentUser%]` without specifying the user.
 * We relaxed the restriction that entities with an online synchronization mode could not refer to entities with an offline synchronization mode. It now only prevents XPath constraints in pages and nanoflows that mix entities with online and offline synchronization modes allowing more modeling possibilities.
-* When [tracing](/refguide/tracing-in-runtime/) is enabled, traces now include spans for all Microflow activities.
+* When [tracing](/refguide/opentelemetry-in-runtime/) is enabled, traces now include spans for all Microflow activities.
 * We bundled OpenTelemetry agent jar with Studio Pro. It can be found under `runtime/agents/opentelemetry-javaagent.jar`.
-* We provided the **Enable Tracing** option to enable runtime tracing in Studio Pro. It can be accessed through **App Settings**. For more information, see the [Minimal Configuration](/refguide/tracing-in-runtime/#min-configuration) section in *Tracing*.
+* We provided the **Enable Tracing** option to enable runtime tracing in Studio Pro. It can be accessed through **App Settings**. For more information, see the [Minimal Configuration](/refguide/opentelemetry-in-runtime/#min-configuration) section in *Tracing*.
 * We no longer close the response writer of custom request handlers, if an asynchronous request is started. With this change it is possible to implement asynchronous request handlers.
 * We implemented an OpenTelemetry agent extension that provides default settings. It can be found under `runtime/agents/mendix-opentelemetry-agent-extension.jar`.
 * We now add consistency warnings if there are multiple versions of the same Java dependency in your app.

content/en/docs/releasenotes/studio-pro/11/11.5.md

@@ -42,7 +42,7 @@ weight: 95
 * When an OQL UPDATE statement has a SET expression that returns multiple rows, Studio Pro now throw a `CardinalityViolationException` instead of a generic `ConnectionBusException`.
 * We improved the way Studio Pro updates attributes and associations based on the OQL query of a view entity. It now renames existing attributes and associations when the expression is the same but the alias is different.
 * We improved the Send REST Request activity in Studio Pro. It now indicates whether parameters are required or not.
-* We implemented a new [Tracing](/refguide/tracing-in-runtime/#testing) feature that allows filtering out spans by their name. 
+* We implemented a new [Tracing](/refguide/opentelemetry-in-runtime/#testing) feature that allows filtering out spans by their name. 
 * We have improved the UX of the managed dependencies and **userlib** *.JAR* exclusions dialogs. Now checking the rows will exclude the JAR files instead of including them.
 * The logout API in the new client `mx-api` now supports an optional params object with `reloadOnSuccess` flag. By default, `mx-api/logout` automatically reloads the page after a successful logout if you call it with no params object. If you pass a params object `{reloadOnSuccess: false}`, the automatic reload is disabled so you can implement your own custom logout flow and trigger reload yourself when needed.
 * Mendix 11 introduces a change in the versioning schema by dropping the fourth element, known as the build number. Versions will now follow a SemVer pattern (`major.minor.patch`) with the occasional pre-release suffix (for example, `beta.1` for planned pre-releases). This semantic version will also be the version that is returned by `Core.getRuntimeVersion()`. Apps built with a pre-release can be identified internally by their exact version.