Merge branch 'development' into update-native-template-release-notes-v14.1.14

Author: vadymv-mendix

content/en/docs/control-center/security/private-connectivity/configure-private-connectivity.md

@@ -343,7 +343,7 @@ Before you can connect to resources running on your own infrastructure, you have
 Mendix Cloud Private Connectivity currently supports exposing physical [subnet routes](https://tailscale.com/kb/1019/subnets) to your network via an agent. This is what you can expose:
 
 * A single IP range, such as `192.0.2.0/24` 
-* Multiple IP ranges separated by a colon, such as `192.0.2.0/24,198.51.100.0/24`
+* Multiple IP ranges separated by a comma, such as `192.0.2.0/24,198.51.100.0/24`
 * A single IP address, such as `10.100.0.5/32`
 
 #### Exposing Subnet Routes on a Windows Server {#private-connectivity-resources-expose-routes-windows}

content/en/docs/deployment/general/mendix-pipelines.md

@@ -49,12 +49,10 @@ The search and filter options allow you to review specific run types. You can do
 * Filter by trigger: All triggers, recurring schedule, Teamserver push (Git), or manual
 * Filter by status: All statuses, pending, succeeded, in progress, or failed
 
-### Run Results
+### Run Details{#run-results}
 
 To see the results of a particular run, click **Details** ({{% icon name="paper-clipboard" %}}).
 
-This page provides an overview of the run details. Clicking an entry expands the executed step, revealing more information about the run; this is particularly useful for debugging failed Mendix Pipeline runs. When a step is expanded, a **View Parameters** button becomes visible, use this to view the input and output parameters and their values.
-
 At the top of the page, there are several cards that display important information, such as whether the run succeeded or failed. If it failed, it includes information about the error that caused the run failure. There are two types of errors: step-level errors and system-level errors.
 
 #### Step-Level Errors
@@ -70,6 +68,18 @@ If a step fails, that step is flagged with an error icon ({{% icon name="alert-t
 System-level errors occur if [user settings](#configure-settings) have not been configured or if an internal Mendix component is down.
 
 If a system-level error occurs, the card in the upper-left corner of the **Details** page identifies the error that caused the run to fail. Click **See details** on the card to view more information about the error.
+
+The run details page also provides an overview of the run. Clicking an entry expands the executed step, revealing more information about the run; this is particularly useful for debugging failed Mendix Pipeline runs. When a step is expanded, a **View Parameters** button becomes visible, use this to view the input and output parameters and their values.
+
+#### AI Log Summary
+
+In addition to **View parameters** button, every executed step, whether successful or failed, includes a **Summarize** button, which when clicked, generates an AI-powered summary of the step run. For failed steps, the summary explains the error and suggests next steps to help resolve the issue.
+
+The summary pane, also includes the following actions:
+
+* **Retry** to regenerate a new AI log summary
+* **Like** or **Dislike** to provide feedback on the AI-generated response
+* **Copy** the AI summary to clipboard
 
 ## The Designs Tab{#designs-tab}
 

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

@@ -12,17 +12,17 @@ There are several application performance monitoring (APM) tools for cloud appli
 
 Mendix provides out-of-the-box configuration to use Datadog, AppDynamics, Dynatrace, Splunk Cloud Platform, and New Relic to provide additional monitoring for your Mendix Apps running on Mendix Cloud.
 
-{{% alert color="info" %}}
-[AppDynamics](https://www.appdynamics.com/) application monitoring is fully supported in Mendix 9.7 and above. For older supported versions, only the basic AppDynamics Java Agent metrics are available, along with the `postgresql` and `mx.client` namespaces.
-
-[Dynatrace](https://www.dynatrace.com/) OneAgent is used to collect metrics. Additionally, in Mendix 9.7 and above, custom application runtime and database metrics are supported.
+The table below summarizes the monitoring capabilities each tool supports:
 
-[Datadog](https://www.datadoghq.com/) logging and application metrics are supported in Mendix 7.15 and above.
+| APM Tool | Logs | Metrics | Traces | Min. Mendix Version |
+| --- | :---: | :---: | :---: | --- |
+| [AppDynamics](https://www.appdynamics.com/) | {{< icon name="remove-circle-filled" color="red" >}} | {{< icon name="checkmark-circle-filled" color="green" >}} | {{< icon name="remove-circle-filled" color="red" >}} | 9.7 |
+| [Dynatrace](https://www.dynatrace.com/) | {{< icon name="checkmark-circle-filled" color="green" >}} | {{< icon name="checkmark-circle-filled" color="green" >}} | {{< icon name="remove-circle-filled" color="red" >}} | 9.7 |
+| [Datadog](https://www.datadoghq.com/) | {{< icon name="checkmark-circle-filled" color="green" >}} | {{< icon name="checkmark-circle-filled" color="green" >}} | {{< icon name="checkmark-circle-filled" color="green" >}} | 7.15 ¹ |
+| [Splunk Cloud Platform](https://www.splunk.com/en_us/products/splunk-cloud-platform.html) | {{< icon name="checkmark-circle-filled" color="green" >}} |{{< icon name="checkmark-circle-filled" color="green" >}} | {{< icon name="remove-circle-filled" color="red" >}} | 9.7 |
+| [New Relic](https://www.newrelic.com/) | {{< icon name="checkmark-circle-filled" color="green" >}} | {{< icon name="checkmark-circle-filled" color="green" >}} | {{< icon name="remove-circle-filled" color="red" >}} | 9.7 |
 
-[Splunk Cloud Platform](https://www.splunk.com/en_us/products/splunk-cloud-platform.html) is supported for analyzing runtime application logs.
-
-[New Relic](https://www.newrelic.com/) logging and application metrics are supported in Mendix 9.7 and above. Custom application runtime and database metrics are supported.
-{{% /alert %}}
+<small>¹ Logs and metrics are available from Mendix 7.15 and above. Tracing requires Mendix 10.24.12 or 11.5 and above.</small>
 
 This document explains what information can be provided to a SaaS-based data analytics platform.
 

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

@@ -136,7 +136,7 @@ The activity name will be one of the following reported activities:
 
 You can use this information during performance optimization. Even when you cannot identify the exact activity (for example, if there are several different `retrieveObject` activities in the same microflow), you can still use this information to identify which activities might be related to trends in performance. You can also use it to compare performance between different versions or environment configurations.
 
-### Custom Tags
+### Custom Tags{#custom-tags}
 
 If you use Datadog to monitor more than one app and environment, you will not be able to tell which app or environment these metrics apply to. To identify the metrics for your app and environment in Datadog, you need to add tags for the app name and environment.
 
@@ -162,18 +162,77 @@ Setting these values for your app causes all metrics from this environment of yo
 You can add more tags if you want, but note that Datadog may charge for custom metrics. For more information, see [Custom Metrics Billing](https://docs.datadoghq.com/account_management/billing/custom_metrics) on the Datadog site.
 {{% /alert %}}
 
+Tags you set here also influence Mendix's pre-configured Datadog variables. In particular, if you include a `service:`, `env:`, or `version:` tag, Mendix uses those values when automatically configuring [Unified Service Tagging](https://docs.datadoghq.com/getting_started/tagging/unified_service_tagging/) for your app. See [Pre-configured Variables](#pre-configured-variables) for details.
+
+## Pre-configured Variables{#pre-configured-variables}
+
+When Datadog is enabled for your Mendix app, Mendix automatically configures a set of Datadog variables on your behalf. Understanding these helps you avoid unexpected behavior and allows you to override them where needed.
+
+Mendix sets the following [Unified Service Tagging](https://docs.datadoghq.com/getting_started/tagging/unified_service_tagging/) variables automatically, deriving their values from your app's configuration:
+
+* `DD_SERVICE` – defaults to your app's name, derived from its domain. You can override this by setting a `service:<name>` tag (for example, `service:customermanagement`) on the **Tags** tab of your environment.
+* `DD_ENV` – set from the `env:` tag if present.
+* `DD_VERSION` – set from the `version:` tag if present; otherwise defaults to the Mendix model version of your application.
+
+### Automatically Configured Variables{#auto-configured-variables}
+
+The following variables are set automatically by Mendix when your app starts. Some can be overridden using [Custom Environment Variables](/developerportal/deploy/environments-details/#custom-environment-variables) if you need different values.
+
+| Variable | Automatically Set To | Can Be Overridden? | Description |
+| --- | --- | --- | --- |
+| `DD_SERVICE` | Defaults to your app's name, derived from its domain. Override via a `service:` tag on the Tags tab. | Yes | Identifies your app as a service in Datadog. Used by APM and Unified Service Tagging. |
+| `DD_ENV` | Value of `env:` tag | Yes | Identifies the environment (for example, `production`, `accp`). Used by Unified Service Tagging. |
+| `DD_VERSION` | Value of `version:` tag, or the Mendix model version | Yes | Identifies the deployed version of your app. Used by Unified Service Tagging. |
+| `DD_TAGS` | All tags from the Tags tab | Yes | Sent as global tags on all metrics, traces, and logs submitted to Datadog. |
+| `DD_HOSTNAME` | `<application-domain>-<pod-name-suffix>` (for example, `customermanagement-accp.mendixcloud.com-c25sj` or `customermanagement.mendixcloud.com-6pxlk`) | No | The hostname shown in Datadog for your app. |
+| `DD_LOGS_ENABLED` | `true` | No | Enables log forwarding to Datadog. |
+| `DD_JMXFETCH_ENABLED` | `true` | No | Enables JMX metric collection from the Mendix runtime via the Datadog Java trace agent. |
+| `DD_SERVICE_MAPPING` | `<database>:<app>.db` | No | Links your database service to your app in Datadog APM, so database calls appear correlated in traces. |
+
+{{% alert color="info" %}}
+Variables marked **No** in the **Can Be Overridden?** column are fixed by Mendix and cannot be changed via Custom Environment Variables.
+{{% /alert %}}
+
 ## Multi-Instance Metrics{#multi-instance-metrics}
 
 To view metrics for multiple instances of an application on the Datadog dashboard, follow these steps:
 
-1. In Datadog, go to **Metrics** > **Explorer**.
+1. In Datadog, go to **Metrics** and click **Explorer**.
 2. In the search form, search for your desired metric.
 3. In the **from** field, specify your desired app environment's **Environment ID**. Use the format `application_name:<environment id>`.
-4. In the **avg by** field, select **instance_index**.
+4. In the **avg by** field, select **pod_name**.
+
+{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-metrics-explorer.png" alt="Metrics Explorer search form" >}}
+
+If the app has more than one instance, you will see lines on the graph for each instance.
+
+## 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.
+
+{{% alert color="info" %}}
+Mendix Tracing requires Mendix Runtime 10.24.12 or above, or 11.5 or above.
+{{% /alert %}}
+
+{{% alert color="warning" %}}
+Enabling Mendix Tracing may significantly affect your Datadog APM costs. Review the [Datadog APM billing page](https://docs.datadoghq.com/account_management/billing/apm_tracing_profiler/) before enabling this feature in production.
+{{% /alert %}}
+
+### Enabling Tracing{#enable-tracing}
+
+To enable Mendix Tracing, follow these steps:
+
+1. From [Apps](https://sprintr.home.mendix.com), go to the **Environments** page of your app.
+2. Click **Details** on the environment you want to monitor.
+3. Switch to the **Runtime** tab.
+4. Click **Add** in the **Custom Environment Variables** section.
+5. Set **Name** to `MX_TRACING_ENABLED` and **Value** to `true`.
+6. Click **Save**.
+7. Redeploy your app into the selected environment.
 
-{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-metrics-explorer.png" alt="Metrics Explorer search form" class="no-border" >}}
+### Filtering Traces{#filter-traces}
 
-If the app has more than one instance, you will see lines on the graph for each instance.  
+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).
 
 ## Additional Information{#additional-info}
 
@@ -213,7 +272,7 @@ You can find the correct type and unit for submitted metrics in the GitHub repo
 
 ### System Metrics{#system-metrics}
 
-System metrics are disabled by default as they usually reflect metrics for a host, rather than for a specific container. You can enable these additional metrics by creating a `DD_ENABLE_CHECKS` custom environment variable and setting its value to `true`. (By default, this variable is set to `false`.)
+System metrics are disabled as they usually reflect metrics for a host, rather than for a specific application container.
 
 ### Datadog Events Explorer
 
@@ -246,6 +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
 * [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