When a configuration change causes issues such as degraded performance or broken functionality, you need to identify what changed and who made the change. Microservices Engine (MSE) records every configuration change for 30 days, enabling you to trace changes and roll back to a previous version. You can view the type, content, and exact update time of each operation.
Prerequisites
Before you begin, make sure that you have:
A Nacos engine instance (V1.2.1 or later). For more information, see Create a Nacos engine
To upgrade an earlier Nacos engine, see Update a Nacos version.
Query version history
-
Log on to the MSE console, and select a region in the top navigation bar.
-
In the left-side navigation pane, choose Microservices Registry > Instances.
-
On the Instances page, click the name of the instance.
In the left-side navigation pane, choose Configuration Management > Versions.
On the Versions page, select a Namespace, specify the Data ID and Group, and then click Query.
NoteBoth Data ID and Group are required fields.
In the query results, find the target version and click View in the Actions column.
Operator identification
The Operated By column identifies who published each version. The displayed value depends on the client version and credentials:
| Client version | Credential provided | Displayed value |
|---|---|---|
| Nacos Client 2.x | AccessKey pair | UID of the operator |
| Nacos Client 2.x | No AccessKey pair | IP address of the operator |
| Nacos Client 1.x (SDK) | N/A | Column not displayed |
Roll back a configuration
If a configuration update causes issues, you can revert to a previous version.
In the query results, find the target version and click Roll Back in the Actions column to roll back the current configuration to a selected historical version.
MSE retains change records for 30 days.