Skip to content

Commit 1a36974

Browse files
Merge pull request mendix#10521 from ekremsekerci/dynatrace_integration_update
Update Dynatrace integration documentation.
2 parents 58db425 + 8895e40 commit 1a36974

5 files changed

Lines changed: 27 additions & 18 deletions

File tree

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

Lines changed: 18 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ For Dynatrace monitoring, [Dynatrace OneAgent](https://www.dynatrace.com/platfor
1414

1515
In addition to auto-instrumented built-in metrics collected by OneAgent, Mendix apps can also collect custom application metrics. Custom application metrics are supported in Mendix 9.7 and above. For more information on the custom metrics you can send to Dynatrace, see [Monitoring Your Mendix Apps with an APM Tool](/developerportal/operate/monitoring-with-apm/).
1616

17+
For Dynatrace SaaS customers, application logs can also be viewed by setting environment variable `DT_ENABLE_LOGS` to `true`.
18+
1719
## Prerequisites
1820

1921
To use Dynatrace and send data to Dynatrace from your Mendix app, you need the following:
@@ -30,20 +32,21 @@ To use Dynatrace and send data to Dynatrace from your Mendix app, you need the f
3032
To start sending your Mendix app's metrics to Dynatrace, you need to set some environment variables in the Mendix Portal. Follow these steps:
3133

3234
1. From [Apps](https://sprintr.home.mendix.com), go to the **Environments** page of your app.
33-
1. Click **Details** on the environment you wish to monitor with Dynatrace.
34-
1. Switch to the [**Runtime** tab](/developerportal/deploy/environments-details/#runtime-tab).
35-
1. Add the following **Custom Environment Variables**.
35+
2. Click **Details** on the environment you wish to monitor with Dynatrace.
36+
3. Switch to the [**Runtime** tab](/developerportal/deploy/environments-details/#runtime-tab).
37+
4. Add the following **Custom Environment Variables**.
3638

3739
| Variable | Required? | Description | Details |
38-
| --- | --- | --- | --- |
39-
| `DT_SAAS_URL` | Yes | The URL of Dynatrace environment | The format when using the Dynatrace SaaS environment is similar to `https://<your-environment-id>.live.dynatrace.com`. If you are using a Dynatrace managed environment, just provide the full URL of the Dynatrace domain, like `https://<your-dynatrace-domain>`. |
40-
| `DT_TENANT` | Yes | The Dynatrace Environment ID | For more information, see the [Environment ID](https://www.dynatrace.com/support/help/get-started/monitoring-environment/environment-id) Dynatrace documentation. |
41-
| `DT_PAAS_TOKEN` | Yes | The access token for integrating your Mendix app with Dynatrace | Create this on the Dynatrace environment. For more information, see [Generate an Access Token](https://www.dynatrace.com/support/help/get-started/access-tokens#create-api-token). The token must include the `PaaS integration - Installer download` and `Ingest metrics` scopes. |
42-
| `DT_IS_MANAGED` | No | Set this to `true` if you are using Dynatrace Managed. The default is assumed to be Dynatrace SaaS and set to `false`. | This variable is only needed for custom application metrics ingestion. |
43-
| `DT_CLUSTER_ID` | No | You can use this to tag your cluster, process group, or deployment group. | |
44-
| `DT_CUSTOM_PROP` | No | This can be used to provide metadata for your process group. | For more information, see [Define Your Own Process Group Metadata](https://www.dynatrace.com/support/help/platform-modules/infrastructure-monitoring/process-groups/configuration/define-your-own-process-group-metadata). |
40+
| --- |-----------| --- | --- |
41+
| `DT_SAAS_URL` | Yes | The URL of Dynatrace environment | The format when using the Dynatrace SaaS environment is similar to `https://<your-environment-id>.live.dynatrace.com`. If you are using a Dynatrace managed environment, just provide the full URL of the Dynatrace domain, like `https://<your-dynatrace-domain>`. |
42+
| `DT_TENANT` | Yes | The Dynatrace Environment ID | For more information, see the [Environment ID](https://www.dynatrace.com/support/help/get-started/monitoring-environment/environment-id) Dynatrace documentation. |
43+
| `DT_PAAS_TOKEN` | Yes | The access token for integrating your Mendix app with Dynatrace | Create this on the Dynatrace environment. For more information, see [Generate an Access Token](https://www.dynatrace.com/support/help/get-started/access-tokens#create-api-token). The token must include the `PaaS integration - Installer download` and `Ingest metrics` scopes. For logging integration, `Ingest logs` scope is also required. |
44+
| `DT_ENABLE_LOGS` | No | Set this to `true` to enable logging | Only supported for Dynatrace SaaS. `Ingest logs` scope is required to be included in the access token. |
45+
| `DT_IS_MANAGED` | No | Set this to `true` if you are using Dynatrace Managed. The default is assumed to be Dynatrace SaaS and set to `false`. | This variable is only needed for custom application metrics ingestion. |
46+
| `DT_CLUSTER_ID` | No | You can use this to tag your cluster, process group, or deployment group. | |
47+
| `DT_CUSTOM_PROP` | No | This can be used to provide metadata for your process group. | For more information, see [Define Your Own Process Group Metadata](https://www.dynatrace.com/support/help/platform-modules/infrastructure-monitoring/process-groups/configuration/define-your-own-process-group-metadata). |
4548

46-
1. Return to the **General** tab and restart your environment.
49+
5. Return to the **General** tab and restart your environment.
4750

4851
## Additional Information {#additional-info}
4952

@@ -70,10 +73,10 @@ You can set extra dimensions as tags in the Mendix Portal. Mendix recommends at
7073
To set this tag, do the following:
7174

7275
1. From [Apps](https://sprintr.home.mendix.com), go to the **Environments** page of your app.
73-
1. Click **Details** ({{% icon name="notes-paper-edit" %}}) on an environment you are monitoring with Dynatrace.
74-
1. Switch to the **Tags** tab.
75-
1. Click **Add** and type in a string to be sent to Dynatrace as a dimension. For more information, see the [**Tags** tab](/developerportal/deploy/environments-details/#tags) documentation in *Environment Details*.
76-
1. Restart the app.
76+
2. Click **Details** ({{% icon name="notes-paper-edit" %}}) on an environment you are monitoring with Dynatrace.
77+
3. Switch to the **Tags** tab.
78+
4. Click **Add** and type in a string to be sent to Dynatrace as a dimension. For more information, see the [**Tags** tab](/developerportal/deploy/environments-details/#tags) documentation in *Environment Details*.
79+
5. Restart the app.
7780

7881
Setting this value for your app causes all metrics from this environment of your app to have these tags. For example, the tags for `mx.microflow.time.avg` for this set of metrics include `env:accp`.
7982

content/en/docs/deployment/mx-azure/mx-azure-licensing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,4 +27,4 @@ After 120 days from an app environment's creation, Mendix begins charging a fixe
2727

2828
### Will I Still Need to Request Runtime Licenses for my Mendix Apps?
2929

30-
Yes. For production environments, you must supply runtime licenses for your Mendix apps to move the Mendix Runtime out of trial mode. This licensing process aligns with how Mendix on Kubernetes works (for example, requesting and applying subscription keys). For more information, see [Licensing Apps outside Mendix Cloud](http://localhost:1313/developerportal/deploy/licensing-apps-outside-mxcloud/).
30+
Yes. For production environments, you must supply runtime licenses for your Mendix apps to move the Mendix Runtime out of trial mode. This licensing process aligns with how Mendix on Kubernetes works (for example, requesting and applying subscription keys). For more information, see [Licensing Apps outside Mendix Cloud](/developerportal/deploy/licensing-apps-outside-mxcloud/).

content/en/docs/releasenotes/deployment/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Follow the links in the table below to see the release notes you want:
1515

1616
| Type of Deployment | Last Updated |
1717
| --- | --- |
18-
| [Mendix Cloud](/releasenotes/developer-portal/mendix-cloud/) | December 14, 2025 |
18+
| [Mendix Cloud](/releasenotes/developer-portal/mendix-cloud/) | December 23, 2025 |
1919
| [Mendix on Kubernetes](/releasenotes/developer-portal/mendix-for-private-cloud/) | November 6, 2025 |
2020
| [Mendix on Azure](/releasenotes/developer-portal/mendix-on-azure/) | November 6, 2025 |
2121
| [SAP Business Technology Platform (SAP BTP)](/releasenotes/developer-portal/sap-cloud-platform/) | August 27, 2024 |

content/en/docs/releasenotes/deployment/mendix-cloud.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,12 @@ For information on the current status of deployment to Mendix Cloud and any plan
1616

1717
## 2025
1818

19+
### December 23, 2025
20+
21+
#### New Features
22+
23+
* We have added logging support to Dynatrace integration.
24+
1925
### December 14, 2025
2026

2127
#### Improvements

layouts/partials/landingpage/latest-releases.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,6 @@ <h4 class="lp-panel-title">Latest Releases</h4>
1414
</li>
1515
<li class="lp-panel-list">
1616
<a href="/releasenotes/developer-portal/deployment/">Deployment</a>
17-
<p class="rn-date">December 14, 2025</p>
17+
<p class="rn-date">December 23, 2025</p>
1818
</li>
1919
</ul>

0 commit comments

Comments
 (0)