Skip to content
Open
17 changes: 15 additions & 2 deletions content/en/docs/deployment/private-cloud/private-cloud-monitor.md
Original file line number Diff line number Diff line change
Expand Up @@ -515,11 +515,24 @@ This way, upgrading an older Mendix Operator will not change the way it generate

### Compatibility Metrics Mode

To enable `compatibility` metrics mode, set the `mode` attribute to `compatibility`.
In this mode, all other `runtimeMetricsConfiguration` attributes are ignored.
To enable `compatibility` metrics mode, set the `mode` attribute to `compatibility`. In this mode, all other `runtimeMetricsConfiguration` attributes are ignored.

{{% alert color="info" %}}
For Operator versions older than 2.27.0 that were upgraded from older versions, the metrics mode in `OperatorConfiguration` is set to `compatibility` to maintain backward compatibility. For new installations with Operator 2.27.0 and later, the metrics mode in `OperatorConfiguration` is set to `native` by default, and the `m2ee-metrics` sidecar is disabled.

When you manually select compatibility mode for a specific environment (overriding the default mode from `OperatorConfiguration`), it becomes your responsibility to manually switch the environment back to native or default mode when needed. This is particularly important when upgrading to Operator version 2.27.0 or newer, as compatibility mode is no longer supported.
{{% /alert %}}

#### Enable Compatibility Metrics in Connected Mode

{{% alert color="info" %}}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FRom line 549 to 552, u are also mentioning that customer wont be able to set the Compatibility mode, may be if u can remove the Alert from here.
U are mentioning the same thing at two different places

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Compatibility mode is only available for Operator versions older than 2.27.0. If you attempt to set compatibility mode for Operator version 2.27.0 or newer, an error message will be displayed:

{{< figure src="/attachments/deployment/private-cloud/compatibility_mode_warning.png" alt="Error message when attempting to set compatibility mode for Operator 2.27.0 and above" >}}

In this case, you must use native mode instead. See [Enable Native Metrics in Connected Mode](#enable-native-metrics-connected-mode) for instructions.
{{% /alert %}}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can u also mention if there is any specific behavior for existing customer who set the mode to compatibility mode. Will they have change in behavior?

1. Open your app in [Apps](https://sprintr.home.mendix.com/).
2. Go to the **Environments** page.
3. Click **Details** next to the environment where compatibility mode should be used.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,12 @@ For information on the current status of deployment to Mendix on Kubernetes and

## 2026

### June 4, 2026

#### Portal Improvements

* We have added a check to prevent enabling **Compatibility Metrics Mode** in **Runtime Metrics Configuration** for Operator version 2.27.0 and above.

### May 21, 2026

#### License Manager CLI v0.10.10 {#0.10.10}
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.