You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 behaviour and allows you to override them where needed.
169
+
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.
170
170
171
171
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:
172
172
173
-
***`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.
174
-
***`DD_ENV`** — set from the `env:` tag if present.
175
-
***`DD_VERSION`** — set from the `version:` tag if present; otherwise defaults to the Mendix model version of your application.
173
+
*`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.
174
+
*`DD_ENV` – set from the `env:` tag if present.
175
+
*`DD_VERSION` – set from the `version:` tag if present; otherwise defaults to the Mendix model version of your application.
@@ -197,21 +197,21 @@ Variables marked **No** in the **Can Be Overridden?** column are fixed by Mendix
197
197
198
198
To view metrics for multiple instances of an application on the Datadog dashboard, follow these steps:
199
199
200
-
1. In Datadog, go to **Metrics**>**Explorer**.
200
+
1. In Datadog, go to **Metrics**and click**Explorer**.
201
201
2. In the search form, search for your desired metric.
202
202
3. In the **from** field, specify your desired app environment's **Environment ID**. Use the format `application_name:<environment id>`.
203
203
4. In the **avg by** field, select **pod_name**.
204
204
205
-
{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-metrics-explorer.png" alt="Metrics Explorer search form" class="no-border" >}}
205
+
{{< figure src="/attachments/deployment/mendix-cloud-deploy/metrics/datadog-metrics/datadog-metrics-explorer.png" alt="Metrics Explorer search form" >}}
206
206
207
207
If the app has more than one instance, you will see lines on the graph for each instance.
208
208
209
209
## Mendix Tracing{#mendix-tracing}
210
210
211
-
[Mendix Tracing](https://docs.mendix.com/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.
211
+
[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.
212
212
213
213
{{% alert color="info" %}}
214
-
Mendix Tracing requires Mendix Runtime version **10.24.12** or later, or **11.5** or later.
214
+
Mendix Tracing requires Mendix Runtime 10.24.12 or above, or 11.5 or above.
215
215
{{% /alert %}}
216
216
217
217
{{% alert color="warning" %}}
@@ -232,7 +232,7 @@ To enable Mendix Tracing, follow these steps:
232
232
233
233
### Filtering Traces{#filter-traces}
234
234
235
-
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](https://docs.mendix.com/refguide/tracing-in-runtime/#filtering) in the Mendix Reference Guide.
235
+
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).
236
236
237
237
## Additional Information{#additional-info}
238
238
@@ -305,7 +305,7 @@ Previously, when Mendix Cloud ran on Cloud Foundry, hosts were incorrectly regis
305
305
306
306
*[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
307
307
*[Metrics](/developerportal/operate/metrics/)
308
-
*[Tracing in Runtime](https://docs.mendix.com/refguide/tracing-in-runtime/) – Mendix documentation
308
+
*[Tracing in Runtime](/refguide/tracing-in-runtime/) – Mendix documentation
0 commit comments