You can view historical version records to trace the changes of configurations over time, and learn about the type, content, and exact update time of each operation. If an issue, such as sudden deterioration in system performance or a feature exception, occurs due to a configuration change, you can quickly roll back the system to the normal state. This prevents service interruptions caused by invalid configurations.
Prerequisites
Microservices Engine (MSE) is activated. For more information, see Activate MSE.
A Nacos instance is created. For more information, see Create a Nacos engine. The Nacos engine version must be V1.2.1 or later. For more information about how to upgrade the Nacos engine version, see Update a Nacos version.
Procedure
Log on to the MSE console and select a region in the top navigation bar.
In the left-side navigation pane, choose .
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 parameters, and then click Query.
NoteYou must specify the Group and Data ID parameters.
In the query result list, the Operated By column lists the unique identifiers (UIDs) of the operators who released the historical versions. If you use Nacos Client 2.x and do not pass an AccessKey pair, the Operated By column displays the IP addresses of the operators. If you use Nacos Client 1.x and the historical versions are released by using SDKs, this column is not displayed.
In the displayed list, find the desired historical configuration version, and click View in the Actions column.
NoteMSE retains change records for 30 days.
What to do next
Roll back a version: In the displayed list, find the desired configuration version, and click Roll Back in the Actions column to roll back the current configuration version to a historical configuration version.