Issue
The application does not start after the MX_TRACING_ENABLED and MX_OTEL_ENABLED custom environment variables are both set to true. Restarting the environment and deploying a new package do not resolve the issue.
The following symptoms occur:
The environment stays stopped or never reaches the running state.
The application log in the Mendix Portal is empty, and no error message points to the cause.
The environment activity does not show a clear failure for the start attempt.
The issue is reproducible after the two variables are enabled again, and the application starts normally after they are removed or set to false.
Environment
Applications hosted in Mendix Cloud
Cause
MX_TRACING_ENABLED and MX_OTEL_ENABLED enable two separate Application Performance Monitoring (APM) integrations that are not designed to run together:
MX_TRACING_ENABLED=trueenables the Mendix Datadog APM integration.MX_OTEL_ENABLED=trueenables the OpenTelemetry integration, which injects an OpenTelemetry Collector sidecar container next to the application.
Both integrations interact with the same Java Virtual Machine (JVM) instrumentation layer. When both are enabled, they conflict during application startup and cause port binding collisions. The conflict prevents the application from starting before the Mendix Runtime writes any log output, which explains the empty logs.
Solution/Workaround
Use only one tracing integration per environment. The following steps remove the conflicting variable and restore the application.
From Mendix Portal, go to the Environments page of the licensed app.
Click Details on the affected environment.
In the Runtime tab, go to Custom Environment Variables.
Remove the variable of the integration that is not required, or set its value to
false. Use one of the following options:For the Mendix Datadog integration, keep
MX_TRACING_ENABLEDset totrueand removeMX_OTEL_ENABLED.For OpenTelemetry-based tracing, keep
MX_OTEL_ENABLEDset totrueand removeMX_TRACING_ENABLED.
Click Save.
Restart the application to apply the changes.
To send OpenTelemetry data to Datadog, use MX_OTEL_ENABLED=true only and configure Datadog through an OpenTelemetry Collector or the Datadog Distribution of OpenTelemetry Collector (DDOT). Do not enable MX_TRACING_ENABLED for this setup.
If the application still does not start after only one variable remains enabled, contact Mendix Support and include the environment details and the time of the last start attempt.
Internal information related
- 291226
- CRE-850, CLDOPS-16144
- CA82XPUQG/p1793201779820929
Additional information
Mendix documentation:
- Datadog for Mendix Cloud
- OpenTelemetry for Mendix Cloud
- Monitoring Your Mendix Apps with an APM Tool
- Tracing in Runtime
Related KBA: Mendix Cloud Application not starting after 15 minutes after new deployment
0 Comments